{"severity":"null","searchText":"text","description":"null","defaultCreator":false,"inbuiltTests": [ {"issueTags": ["Business logic" ],"issueImpact":"text","superCategory": {"severity": {"_name":"HIGH" },"displayName":"Broken Object Level Authorization (BOLA)","name":"SSRF","shortName":"Broken Function Level Authorization" },"references":"null","_name":"ADD_PUT_METHOD_OVERRIDE_HEADERS","name":"ADD_PUT_METHOD_OVERRIDE_HEADERS","issueDetails":"\"The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing CSV upload parameter with url that redirects to AWS IMDS endpoint. The application responded with 2XX success code and also gave out sensitive AWS information in response. Server-Side Request Forgery (SSRF) flaws occur whenever an API is fetching a remote resource without validating the user-supplied URL. It allows an attacker to coerce the application to send a crafted request to an unexpected destination, even when protected by a firewall or a VPN.\\n \"Modern concepts in application development make SSRF more common and more dangerous.\\n\" \"More common - the following concepts encourage developers to access an external resource based on user input: Webhooks, file fetching from URLs, custom SSO, and URL previews.\\n\" \"More dangerous - Modern technologies like cloud providers, Kubernetes, and Docker expose management and control channels over HTTP on predictable, well-known paths. Those channels are an easy target for an SSRF attack.\\n\" \"It is also more challenging to limit outbound traffic from your application, because of the connected nature of modern applications.\\n\" + \"The SSRF risk can not always be completely eliminated. While choosing a protection mechanism, it is important to consider the business risks and needs.\"\n","issueDescription":"Quite often, APIs do not impose any restrictions on the size or number of resources that can be requested by the user.","testName":"BFLA by HTTP DELETE method overriding" } ],"categories": [ {"severity": {"_name":"HIGH" },"_name":"SSRF","displayName":"Improper Assets Management (IAM)","name":"SSRF","shortName":"Broken Function Level Authorization" } ],"testSourceConfigs":"null","category":"null","subcategory":"null","searchResults": [ {"severity": {"_name":"HIGH" },"creator":"default","addedEpoch":1679402464,"description":"text","id":"https://github.com/akto-api-security/tests-library/blob/master/Misconfiguration/configs/appspec-yml-disclosure.yaml","category": {"severity": {"_name":"HIGH" },"_name":"INJ","displayName":"Broken Object Level Authorization (BOLA)","name":"INJ","shortName":"Injection" },"subcategory":"redirect","tags":"null" } ],"url":"null","tags":"null"}
POST request for endpoint /api/fetchAffectedEndpoints