Skip to content
OpenAdvisories

Weakness (CWE)

CWE-354: Improper Validation of Integrity Check Value

Base Draft

The product does not validate or incorrectly validates the integrity check values or "checksums" of a message.

How to prevent it (1 mitigation)
  1. Implementation

    The protocol specification describes the algorithm used for calculating the checksum. It is then a matter of implementing the calculation and verifying that the calculated checksum and the received checksum match.

Source: MITRE CWE-354

167 results · Feed

  • Medium 5.5

    Windows File Signature Security Feature Bypass Vulnerability

    A security feature bypass exists when Windows incorrectly validates CAB file signatures. An attacker who successfully exploited this vulnerability could inject code into a CAB file without invalidating the file's signature. To exploit the vulnerability, an at…

  • Low 3.1

    The Libreswan Project has found a vulnerability in the processing of IKEv1 informational exchange packets which are enc…

  • Unscored —

    Open Shortest Path First (OSPF) protocol implementations may improperly determine LSA recency in affected Quagga and downstream implementations (SUSE, openSUSE, and Red Hat packages)

    Open Shortest Path First (OSPF) protocol implementations may improperly determine Link State Advertisement (LSA) recency for LSAs with MaxSequenceNumber. According to RFC 2328 section 13.1, for two instances of the same LSA, recency is determined by first com…

  • Medium 5.9

    tlslite-ng off-by-one error on mac checking

    tlslite-ng version 0.7.3 and earlier, since commit d7b288316bca7bcdd082e6ccff5491e241305233 contains a CWE-354: Improper Validation of Integrity Check Value vulnerability in TLS implementation, tlslite/utils/constanttime.py: ct_check_cbc_mac_and_pad(); line "…

  • Medium 4.4

    Bouncy Castle BKS-V1 keystore files vulnerable to trivial hash collisions

    The default BKS keystore use an HMAC that is only 16 bits long, which can allow an attacker to compromise the integrity of a BKS keystore. Bouncy Castle release 1.47 changes the BKS format to a format which uses a 160 bit HMAC instead. This applies to any BKS…

  • Unscored —

    An Improper Validation of Integrity Check Value issue was discovered in PHOENIX CONTACT mGuard firmware versions 7.2 to…

  • Low 3.1

    Nimbus JOSE+JWT vulnerable to padding oracle attack

    Nimbus JOSE+JWT before 4.39 proceeds improperly after detection of an invalid HMAC in authenticated AES-CBC decryption, which allows attackers to conduct a padding oracle attack.