VYPR

CWE-354

Improper Validation of Integrity Check Value

BaseDraftLikelihood: Medium

Description

The product does not validate or incorrectly validates the integrity check values or "checksums" of a message. This may prevent it from detecting if the data has been modified or corrupted in transmission.

Improper validation of checksums before use results in an unnecessary risk that can easily be mitigated. The protocol specification describes the algorithm used for calculating the checksum. It is then a simple matter of implementing the calculation and verifying that the calculated checksum and the received checksum match. Improper verification of the calculated checksum and the received checksum can lead to far greater consequences.

Hierarchy (View 1000)

Children

none

Related attack patterns (CAPEC)

CAPEC-145 · CAPEC-463 · CAPEC-75

CVEs mapped to this weakness (183)

page 10 of 10
  • CVE-2023-31438MedJun 13, 2023
    risk 0.00cvss 5.3epss 0.00

    An issue was discovered in systemd 253. An attacker can truncate a sealed log file and then resume log sealing such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security…

  • CVE-2021-3772MedMar 2, 2022
    risk 0.00cvss 6.5epss 0.01

    A flaw was found in the Linux SCTP stack. A blind attacker may be able to kill an existing SCTP association through invalid chunks if the attacker knows the IP-addresses and port numbers being used and the attacker can send packets with spoofed IP addresses.

  • CVE-2020-25862HigOct 6, 2020
    risk 0.00cvss 7.5epss 0.02

    In Wireshark 3.2.0 to 3.2.6, 3.0.0 to 3.0.13, and 2.6.0 to 2.6.20, the TCP dissector could crash. This was addressed in epan/dissectors/packet-tcp.c by changing the handling of the invalid 0xFFFF checksum.