CyberSecBulletin
CVE-2024-3596NVD status: Modified

RFC: Improper Validation of Integrity Check Value

Published Updated By the CyberSecBulletin desk

CVE-2024-3596 is a critical-severity improper validation of integrity check value vulnerability in RFC from IETF, with a CVSS 3.1 base score of 9.0 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected RFC versions: 2865. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 14.9% chance of exploitation within 30 days, which is in the top 3.25% of all scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update CPC80 Central Processing/Communication to V16.51 or a later version.
  2. Update CPCI85 Central Processing/Communication to V6.20 or a later version.
  3. Update POWER METER SICAM Q100 family to V2.70 or a later version.
  4. Read the advisory on psirt.global.sonicwall.com for workarounds and exact fixed builds.
  5. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
IETFRFC2865Not stated
SiemensCPC80 Central Processing/Communicationbefore V16.51V16.51
SiemensCPCI85 Central Processing/Communicationbefore V6.20V6.20
SiemensPOWER METER SICAM Q100 familybefore V2.70V2.70
SiemensPOWER METER SICAM Q200 familybefore V2.83V2.83
SiemensPowerlink IPbefore V4.23V4.23
SiemensRUGGEDCOM APE1808all versionsNot stated
SiemensSICAM AK 3Not specified in the recordNot stated
SiemensSICAM BCNot specified in the recordNot stated
SiemensSICAM GridEdge (Classic)Not specified in the recordNot stated
SiemensSICAM GridEdge Applications for SICAM 8 PlatformNot specified in the recordNot stated
SiemensSICAM GridPassbefore V2.50V2.50
SiemensSICAM TMNot specified in the recordNot stated
SiemensSICORE Base systembefore V2.20.0V2.20.0
SiemensSIPROTEC 5 - CP200 DevicesNot specified in the recordNot stated
SiemensSIPROTEC 5 6MD84 (CP300)before V10.0V10.0
SiemensSIPROTEC 5 6MD85 (CP300)V7.80 up to, but not including, V10.0V10.0
SiemensSIPROTEC 5 6MD86 (CP300)V7.80 up to, but not including, V10.0V10.0
SiemensSIPROTEC 5 6MD89 (CP300)V7.80 up to, but not including, V10.0V10.0
SiemensSIPROTEC 5 6MD89 (CP300) V9.6xbefore V9.68V9.68
SiemensSIPROTEC 5 6MU85 (CP300)before V10.0V10.0
SiemensSIPROTEC 5 7KE85 (CP300)V7.80 up to, but not including, V10.0V10.0
SiemensSIPROTEC 5 7SA82 (CP100)V7.80 up to, but not including, V8.90V8.90
SiemensSIPROTEC 5 7SA82 (CP150)before V10.0V10.0
SiemensSIPROTEC 5 7SA86 (CP300)V7.80 up to, but not including, V10.0V10.0

Version data comes from the organisation that assigned the CVE; 35 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
HighSuccess depends on conditions outside the attacker's control.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.19.0CriticalNVD
CVSS 3.19.0CriticalCISA (ADP)

Official description

RADIUS Protocol under RFC 2865 is susceptible to forgery attacks by a local attacker who can modify any valid Response (Access-Accept, Access-Reject, or Access-Challenge) to any other response using a chosen-prefix collision attack against MD5 Response Authenticator signature.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Validation of Integrity Check Value

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

How developers prevent this class of flaw

  • 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.

More Improper Validation of Integrity Check Value vulnerabilities (CWE-354)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Improper Validation of Integrity Check Value vulnerabilities

Spotted an error? Tell us.