Use of Less Trusted SourceID: 348 | Date: (C)2012-05-14 (M)2022-10-10 |
Type: weakness | Status: DRAFT |
Abstraction Type: Base |
Description
The software has two different sources of the same data or
information, but it uses the source that has less support for verification, is
less trusted, or is less resistant to attack.
Applicable PlatformsLanguage Class: All
Time Of Introduction
- Architecture and Design
- Implementation
Related Attack Patterns
Common Consequences
Scope | Technical Impact | Notes |
---|
Access_Control | Bypass protection
mechanismGain privileges / assume
identity | An attacker could utilize the untrusted data source to bypass
protection mechanisms and gain access to sensitive data. |
Detection MethodsNone
Potential MitigationsNone
Relationships
Related CWE | Type | View | Chain |
---|
CWE-348 ChildOf CWE-907 | Category | CWE-888 | |
Demonstrative Examples (Details)
- This code attempts to limit the access of a page to certain IP
Addresses. It checks the 'HTTP_X_FORWARDED_FOR' header in case an authorized
user is sending the request through a proxy.
Observed Examples
- CVE-2001-0860 : Product uses IP address provided by a client, instead of obtaining it from the packet headers, allowing easier spoofing.
- CVE-2004-1950 : Web product uses the IP address in the X-Forwarded-For HTTP header instead of a server variable that uses the connecting IP address, allowing filter bypass.
- BID:15326 : Similar to CVE-2004-1950
- CVE-2001-0908 : Product logs IP address specified by the client instead of obtaining it from the packet headers, allowing information hiding.
- CVE-2006-1126 : PHP application uses IP address from X-Forwarded-For HTTP header, instead of REMOTE_ADDR.
For more examples, refer to CVE relations in the bottom box.
White Box Definitions None
Black Box Definitions None
Taxynomy Mappings
Taxynomy | Id | Name | Fit |
---|
PLOVER | | Use of Less Trusted Source | |
References:None