APIs Findings.
16 findings in APIs, each written up as a report carries it: what the weakness is and what it lets an attacker do, the fix, CVSS 3.1 and 4.0 ratings, the CWE and the references.
High3
API Endpoint Accessible Without AuthenticationCVSS 8.2 · CWE-306API endpoints that return non-public data or perform actions respond to requests that carry no credentials, so anyone who can reach the API can use them.Broken Function-Level Authorisation (BFLA)CVSS 8.1 · CWE-862API functions meant for administrators or other privileged roles do not check the caller's role, so an ordinary user can call them directly.Broken Object-Level Authorisation (BOLA)CVSS 7.1 · CWE-639API endpoints act on the object identifier supplied in the request without checking that the caller may access that object, so users can read or change other users' records.
Medium8
Deprecated API Versions Still AccessibleCVSS 5.4 · CWE-424Older or deprecated versions of the API remain deployed and reachable alongside the current one, without the security fixes and controls added since.Unrestricted Access to Sensitive Business FlowsCVSS 5.4 · CWE-799A business process such as buying limited stock, booking, signing up or redeeming offers can be automated at scale through the API, with nothing to detect or limit the abuse.GraphQL Query Depth or Batching Not LimitedCVSS 5.3 · CWE-770The GraphQL server places no limit on query depth, complexity, aliases or batched operations, so one request can exhaust server resources or carry thousands of guesses.No Rate Limiting on API EndpointsCVSS 5.3 · CWE-770API endpoints accept an unlimited number, rate or size of requests from a single client, which allows resource exhaustion, guessing attacks, data harvesting and runaway costs.Unsafe Consumption of Third-Party APIsCVSS 4.8 · CWE-20The application trusts data and responses from third-party APIs it calls without validating them, so a compromised or impersonated provider can attack the application through them.Weak or Non-Expiring API KeysCVSS 4.8 · CWE-1391API keys are short, predictable or derived from known values, or never expire and cannot easily be rotated, so a guessed or leaked key gives lasting access to the API.Excessive Data Exposure in API ResponsesCVSS 4.3 · CWE-213API responses return more properties than the client needs, including sensitive ones, and rely on the client to hide them, so anyone reading the raw response sees them.HTTP Method Override AcceptedCVSS 4.3 · CWE-436The API honours headers or parameters that change the HTTP method of a request, so controls applied to the method as sent, by a proxy, firewall or the application, can be bypassed.
Low1
Informational4
API Documentation Publicly ExposedCVSS 0 · CWE-538Interactive documentation or the machine-readable definition of an API that is not meant to be public, such as Swagger UI or an OpenAPI file, can be retrieved by anyone.GraphQL Field Suggestions EnabledCVSS 0 · CWE-209The GraphQL server's error messages suggest valid field and type names for misspelt ones, which lets the schema be reconstructed even when introspection is disabled.GraphQL Introspection EnabledCVSS 0 · CWE-497The GraphQL endpoint answers introspection queries in production, returning its complete schema: every query, mutation, type and field, including ones the client never uses.gRPC Server Reflection EnabledCVSS 0 · CWE-497The gRPC server exposes the reflection service, so anyone who can connect can list every service and method and download the message definitions needed to call them.
The Other Areas
Web Applications 87Authentication and Sessions 32TLS and Certificates 20Network Services 56Internal Networks 9Active Directory 44Windows and Linux Hosts 29Patching and Outdated Software 36AWS 19Azure and Microsoft 365 19Google Cloud 11Containers and Kubernetes 17Mobile Applications 22Wireless 11Email and DNS 11Thick Clients 11Source Code and Supply Chain 13AI and LLM Applications 8Social Engineering and Physical 14IoT and OT 5