Title: Unsecured Vulnerability on GET:/api/v1/primary-transaction
Project: GCPsanity
Description: The unsecured exploit gives an attacker full access to the vulnerable endpoint without credentials.
Assertion
Name: Unsecured Endpoints ( 1 )
Overview: RESTful API is an application program interface (API) that uses HTTP requests to GET, PUT, POST, and DELETE data. A RESTful API — also referred to as a RESTful web service — is based on representational state transfer (REST) technology, an architectural style and approach to communications often used in web services development. These exposed endpoints should not be open to all and should be protected. A top priority for the organizations is to have Secured Endpoints.
The 'Unsecured Endpoint' scanning identifies vulnerabilities resulting from the non-protected endpoints. These endpoints requires no authentication scheme and are open for both authenticated and non-authenticated requests.
Authentication mechanisms are often implemented incorrectly, allowing attackers to compromise authentication tokens or to exploit implementation flaws to assume other user's identities temporarily or permanently. Compromising system's ability to identify the client/user, compromises API security overall.
Security misconfiguration is commonly a result of insecure default configurations, incomplete or ad-hoc configurations, open cloud storage, misconfigured HTTP headers, unnecessary HTTP methods, permissive Cross-Origin resource sharing (CORS), and verbose error messages containing sensitive information.
Severity: The difficulty of achieving API security has increased exponentially and unprotected APIs are one of the top web application security risks organizations face. OWASP included “Unprotected APIs” in its proposal for 2017 top 10 list. ( 2 )
Vulnerability Impact: Every exposed API end-point will have some action to be performed thru appropriate HTTP method and not all methods are valid for every single end-point. Left unchecked and opened for access to all, the following are some of the consequences ( 3 ).
Unnecessary Data Exposure and Data theft and corruption
Denial of Service Attacks – can render your RESTful API into non-functional state
Malicious Code Injection – including SQL Injections
Anti-Farming – RESTful APIs should be prevented from excessive farming.
Exploitation: Almost all kinds of authentication, injection, encryption, configuration, access control, and other issues can possible in the RESTful APIs as like the traditional application. Since APIs includes complex data structures and protocols, the security testing may become cumbersome for an attacker. But it is quite possible to analyze APIs and discover vulnerabilities and exploit ( 4 ).
Remediation: The following techniques may be utilized for having Secured Endpoints ( 3 ) ( 5 ) ( 6 ).
Title: Unsecured Vulnerability on GET:/api/v1/primary-transaction Project: GCPsanity Description: The unsecured exploit gives an attacker full access to the vulnerable endpoint without credentials.
Assertion Name: Unsecured Endpoints ( 1 )
Overview: RESTful API is an application program interface (API) that uses HTTP requests to GET, PUT, POST, and DELETE data. A RESTful API — also referred to as a RESTful web service — is based on representational state transfer (REST) technology, an architectural style and approach to communications often used in web services development. These exposed endpoints should not be open to all and should be protected. A top priority for the organizations is to have Secured Endpoints.
The 'Unsecured Endpoint' scanning identifies vulnerabilities resulting from the non-protected endpoints. These endpoints requires no authentication scheme and are open for both authenticated and non-authenticated requests.
Authentication mechanisms are often implemented incorrectly, allowing attackers to compromise authentication tokens or to exploit implementation flaws to assume other user's identities temporarily or permanently. Compromising system's ability to identify the client/user, compromises API security overall.
Security misconfiguration is commonly a result of insecure default configurations, incomplete or ad-hoc configurations, open cloud storage, misconfigured HTTP headers, unnecessary HTTP methods, permissive Cross-Origin resource sharing (CORS), and verbose error messages containing sensitive information.
Severity: The difficulty of achieving API security has increased exponentially and unprotected APIs are one of the top web application security risks organizations face. OWASP included “Unprotected APIs” in its proposal for 2017 top 10 list. ( 2 )
Vulnerability Impact: Every exposed API end-point will have some action to be performed thru appropriate HTTP method and not all methods are valid for every single end-point. Left unchecked and opened for access to all, the following are some of the consequences ( 3 ).
Exploitation: Almost all kinds of authentication, injection, encryption, configuration, access control, and other issues can possible in the RESTful APIs as like the traditional application. Since APIs includes complex data structures and protocols, the security testing may become cumbersome for an attacker. But it is quite possible to analyze APIs and discover vulnerabilities and exploit ( 4 ).
Remediation: The following techniques may be utilized for having Secured Endpoints ( 3 ) ( 5 ) ( 6 ).
Risk: Unsecured Severity: Critical API Endpoint: http://netbanking.apisec.ai:8080/api/v1/primary-transaction Environment: Master Playbook: ApiV1PrimaryTransactionGetAnonymousInvalid Researcher:
QUICK TIPS
Suggestion: Make sure the endpoint is secured as part of the authentication framework. Effort Estimate: 4.0 Hrs Wire Logs:
IMPORTANT LINKS
Vulnerability Details: https://35.222.190.150/#/app/projects/8a8481a980fb156f01811979aaed388e/recommendations/8a8481a980fb156f01811983cd0b6243/details
Project: https://35.222.190.150/#/app/projects/8a8481a980fb156f01811979aaed388e/jobs
Environment: https://35.222.190.150/#/app/projects/8a8481a980fb156f01811979aaed388e/environments/null/edit
Scan Dashboard: https://35.222.190.150/#/app/projects/8a8481a980fb156f01811979aaed388e/jobs/8a8481a980fb156f01811979cdc93a14/runs/8a8481a980fb156f0181198232bd620c
Playbook: https://35.222.190.150/#/app/projects/8a8481a980fb156f01811979aaed388e/template/ApiV1PrimaryTransactionGetAnonymousInvalid
Coverage: https://35.222.190.150/#/app/projects/8a8481a980fb156f01811979aaed388e/configuration
Code Sample: https://35.222.190.150/#/app/projects/8a8481a980fb156f01811979aaed388e/recommendations/8a8481a980fb156f01811983cd0b6243/codesamples
PS: Please contact support@apisec.ai for apisec access and login issues.
--- apisec Bot ---