-
Notifications
You must be signed in to change notification settings - Fork 183
JSON Hijacking
Sam Sanoop edited this page Sep 13, 2020
·
3 revisions
JSON Hijacking as the name suggests is anattack similar to Cross-Site Request Forgery where an attacker can access cross-domainsensitive JSON data from applications that return sensitive data as arrayliterals to GET requests.
Within the http://dvws.local/passphrasegen.html
, area, a request is made to get passphrase generated by a particular user. This request can be seen below.
It is possible to steal this information due to the following reason:
- Data is returned with the Content Type being
Content-Type: application/json
(No charset specified) - Data is returned inside
[]
array - No authentication is needed to make the above request (Access Control Issue)
Note: JSON Hijacking has been remediated in most modern browsers
- XML External Entity Injection
- Server Side Request Forgery (SSRF)
- Username Enumeration
- NoSQL Injection
- Insecure Direct Object Reference
- Mass Assignment
- Cross Site Scripting (XSS)
- Hidden API Functionality Exposure
- SQL Injection
- Information Disclosure
- Insecure PostMessage Configuration
- Command Injection
- Prototype Pollution
- JSON Hijacking
- XPath Injection
- Cross Origin Resource-Sharing Misonfiguration
- JWT Secret Key Brute Force
- Vertical Access Control
- Horizontal Access Control
- Open Redirect
- Path Traversal
- Unsafe Deserialization
- Sensitive Data Exposure
- Arbitrary File Write
- Introspection Enabled
- GraphQL Access Control Issues
- GraphQL Batching Brute Force
- Client Side Template Injection