Weakness (CWE)
CWE-474: Use of Function with Inconsistent Implementations
The code uses a function that has inconsistent implementations across operating systems and versions.
More detail
The implementation of many functions varies by platform, and at times, even by different versions of the same platform. Implementation differences can include:
- Slight differences in the way parameters are interpreted, leading to inconsistent results.
- Some implementations of the function carry significant security risks.
- The function might not be defined on all platforms.
- The function might change which return codes it can provide, or change the meaning of its return codes.
How to prevent it (1 mitigation)
-
Architecture and Design, Requirements
Do not accept inconsistent behavior from the API specifications when the deviant behavior increases the risk level.
Source: MITRE CWE-474
5 results · Clear filters · Feed
-
Medium 6.8
The Ingenic T41, and probably also T32, T40, and A1 SoC boot ROMs parse and execute an attacker-controlled init table f…
-
Medium 6.5
Inappropriate implementation in WebView in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker to…
-
Medium 4.3
Inappropriate implementation in HTML in Google Chrome prior to 127.0.6533.72 allowed a remote attacker who convinced a …
-
Medium 4.3
Inappropriate implementation in Downloads in Google Chrome prior to 123.0.6312.58 allowed a remote attacker to perform …
-
Medium 5.3
Junos OS: QFX5000 Series and EX4600 Series: Enhanced storm control might not work leading to partial Denial of Service
A vulnerability in Juniper Networks Junos OS, which only affects the release 18.4R2-S5, where a function is inconsistently implemented on Juniper Networks Junos QFX5000 Series and EX4600 Series, and if "storm-control enhanced" is configured, can lead to the e…