Back to list

Improper Assets Management - Version in Query String

Description

Improper assets management, particularly versioning through query strings, poses a security vulnerability by exposing sensitive information and allowing attackers to manipulate application behavior. This vulnerability occurs when sensitive data, such as database identifiers or access tokens, are included in URLs as query parameters, making them susceptible to interception or exploitation. To mitigate this risk, developers should avoid exposing sensitive data in URLs, use secure methods for parameter passing, and implement access controls to restrict unauthorized access to sensitive resources.

Remediation

Refrain from embedding sensitive or version-specific information directly in query strings. Instead, use secure channels such as HTTP headers or encrypted request bodies. Implement strict access controls and authentication to ensure only authorized users can access critical resources. Regularly update and patch software components, and maintain an accurate inventory of all versions in use. If older versions must remain available for legacy support, isolate them to minimize exposure. Employ a Web Application Firewall (WAF) or intrusion detection system to identify and block attempts at leveraging version information in query parameters for malicious purposes. Periodically audit endpoint definitions and logs to confirm that no unintended or sensitive query parameters are exposed.

References

https://owasp.org/Top10/A06_2021-Vulnerable_and_Outdated_Components/https://cwe.mitre.org/data/definitions/937.html

Severity

MEDIUM

Owasp

Code: A06:2021

Category: Vulnerable and Outdated Components

Classification

CWE-937
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

7

CVSS:4.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

7