Republished vendor advisory. This ICSA is a verbatim republication of Siemens ProductCERT SSA-723487 from a direct conversion of the vendor's Common Security Advisory Framework (CSAF) advisory. This is republished to CISA's website as a means of increasing visibility and is provided "as-is" for informational purposes only. CISA is not responsible for the editorial or technical accuracy of republished advisories and provides no warranties of any kind regarding any information contained within this advisory. Further, CISA…
General Recommendations: As a general security measure, Siemens strongly recommends to protect network access to devices with appropriate mechanisms. In order to operate the devices in a protected IT environment, Siemens recommends to configure the environment according to Siemens' operational guidelines for Industrial Security (Download: https://www.siemens.com/cert/operational-guidelines-industrial-security), and to follow the recommendations in the product manuals. Additional information on Industrial Security by Siemens can be found at: https://www.siemens.com/industrialsecurity
Additional Resources: For further inquiries on security vulnerabilities in Siemens products and solutions, please contact the Siemens ProductCERT: https://www.siemens.com/cert/advisories
Credit: Siemens ProductCERT
From CISA's machine-readable CSAF 2.0 advisory (JSON).
| CVE | Weakness | CVSS v3 | Details |
|---|---|---|---|
| CVE-2024-3596 | CWE-924 Improper Enforcement of Message Integrity During Transmission in a Communication Channel | 9.0 Critical |
CVE-2024-3596 RADIUS Protocol under RFC 2865 is susceptible to forgery attacks by a local attacker who can modify responses Access-Reject or Access-Accept using a chosen-prefix collision attack against MD5 Response Authenticator signature. Mitigation: Configure the RADIUS server to require the presence of a Message-Authenticator attribute in all Access-Request packets from RADIUS client devices that support it Mitigation: Restrict access to the networks where RADIUS messages are exchanged (e.g., send RADIUS traffic via management network or a dedicated VLAN) No fix planned: Currently no fix is planned Affected, fixed & timelineAffected:
No fix available: Currently no fix is available Vendor fix: Update to V1.0 SP2 Update 4 or later version Vendor fix: Update to V1.3 or later version Vendor fix: Update to V2.17.0 or later version Vendor fix: Update to V3.0.0 or later version Vendor fix: Update to V3.2 or later version Vendor fix: Update to V3.2 or later version Vendor fix: Update to V4.1.9 or later version Vendor fix: Update to V4.3.11 or later version Vendor fix: Update to V4.6 or later version Vendor fix: Update to V5.10.0 or later version Vendor fix: Update to V5.6 or later version Vendor fix: Update to V6.6.0 or later version Vendor fix: Update to V8.2 or later version |
Scores and weakness types are as CISA or the republishing vendor stated them in this advisory; the linked CVE pages carry the independently enriched CVSS and SSVC assessments.
No coverage found in monitored research blogs or news feeds.
| CVE | CVSS | Affected |
|---|---|---|
| CVE-2024-3596 | 9.0 Critical | IETF RFC RADIUS Protocol under RFC 2865 is susceptible to forgery attacks by a local attacker who can modify any valid Response (Access-Accept, Access-Reject,… |
Named by the advisory itself. Each CVE links to its tracked detail page.
Each vendor links to its Known Exploited Vulnerabilities catalog page. Only vendors that appear in the KEV catalog are listed, either because the publication cites one of their KEV entries or because it names them directly.