Improper Following of Specification by Caller
CWE-573
The product does not follow or incorrectly follows the specifications as required by the implementation language, environment, framework, protocol, or platform.
We track 3 vulnerabilities of this type. 100% are rated high or critical, and the average CVSS score is 8.0.
How this weakness is prevented
- Implementation: When leveraging external functionality, such as an API, it is important that the caller does so in accordance with the requirements of the external functionality.
Latest Improper Following of Specification by Caller vulnerabilities
- 9.1 Critical severity
zebra: Improper Following of Specification by Caller
ZEBRA is a Zcash node written entirely in Rust. Prior to zebrad version 4.3.1 and prior to zebra-script version 5.0.2, after a refactoring, Zebra failed to validate a consensus rule that restricted the possible values of sighash hash types for V5 transactions
- 7.5 High severity
authlib: Improper Validation of Integrity Check Value
Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to version 1.6.9, a library-level vulnerability was identified in the Authlib Python library concerning the validation of OpenID Connect (OIDC) ID Tokens. Specifically, the intern
- 7.5 High severity
Junos OS: Improper Following of Specification by Caller
An Improper Following of Specification by Caller vulnerability in web management (J-Web, Captive Portal, 802.1X, Juniper Secure Connect (JSC) of Juniper Networks Junos OS on SRX Series, EX Series, MX240, MX480, MX960, QFX5120 Series, allows an unauthenticated,