BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-41996High confidence

n/a — Improper Certificate Validation

Unknown · Unknown

Official source article: Siemens SSA-485750 ↗. Check the applicable product and release in the original source.

7.5HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 18 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 1.08% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 18 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

4 current
CVE-2024-41996 · CSAF 2.0 · revision 62 · interimSUSE Product Security TeamCVE-2024-41996
15 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP3 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
  • SLES 15 SP4 CHOST Images for Google
  • SLES 15 SP5 CHOST Images for Google
  • SLES 15 SP1 CHOST Images for Microsoft Azure
  • SLES 15 SP2 CHOST Images for Microsoft Azure
Summary
Validating the order of the public keys in the Diffie-Hellman Key Agreement Protocol, when an approved safe prime is used, allows remote attackers (from the client side) to trigger unnecessarily expensive server-side DHE modular-exponentiation calculations. The client may cause asymmetric resource consumption. The basic attack scenario is that the client must claim that it can only communicate with DHE, and the server must be configured to allow DHE and validate the order of the public key.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-265688 · CSAF 2.0 · revision 13 · interimSiemens ProductCERTSSA-265688: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 TM MFP V1.1
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
Summary
Validating the order of the public keys in the Diffie-Hellman Key Agreement Protocol, when an approved safe prime is used, allows remote attackers (from the client side) to trigger unnecessarily expensive server-side DHE modular-exponentiation calculations. The client may cause asymmetric resource consumption. The basic attack scenario is that the client must claim that it can only communicate with DHE, and the server must be configured to allow DHE and validate the order of the public key.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
SSA-485750 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-485750: Multiple Vulnerabilities in SIDIS Prime Before V4.0.800
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIDIS Prime
Summary
Validating the order of the public keys in the Diffie-Hellman Key Agreement Protocol, when an approved safe prime is used, allows remote attackers (from the client side) to trigger unnecessarily expensive server-side DHE modular-exponentiation calculations. The client may cause asymmetric resource consumption. The basic attack scenario is that the client must claim that it can only communicate with DHE, and the server must be configured to allow DHE and validate the order of the public key.
Remediation
Update to V4.0.800 or later version
SSA-089022 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-089022: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.3
16 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • RUGGEDCOM RST2428P (6GK6242-6PA00)
  • SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
  • SCALANCE XCH328 (6GK5328-4TS01-2EC2)
  • SCALANCE XCM324 (6GK5324-8TS01-2AC2)
  • SCALANCE XCM328 (6GK5328-4TS01-2AC2)
  • SCALANCE XCM332 (6GK5332-0GA01-2AC2)
  • SCALANCE XRH334 (24 V DC, 8xFO, CC) (6GK5334-2TS01-2ER3)
  • SCALANCE XRM334 (230 V AC, 12xFO) (6GK5334-3TS01-3AR3)
  • SCALANCE XRM334 (230 V AC, 8xFO) (6GK5334-2TS01-3AR3)
  • SCALANCE XRM334 (230V AC, 2x10G, 24xSFP, 8xSFP+) (6GK5334-5TS01-3AR3)
  • SCALANCE XRM334 (24 V DC, 12xFO) (6GK5334-3TS01-2AR3)
  • SCALANCE XRM334 (24 V DC, 8xFO) (6GK5334-2TS01-2AR3)
Summary
Validating the order of the public keys in the Diffie-Hellman Key Agreement Protocol, when an approved safe prime is used, allows remote attackers (from the client side) to trigger unnecessarily expensive server-side DHE modular-exponentiation calculations. The client may cause asymmetric resource consumption. The basic attack scenario is that the client must claim that it can only communicate with DHE, and the server must be configured to allow DHE and validate the order of the public key.
Remediation
Update to V3.3 or later version
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-39313

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 18 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

Validating the order of the public keys in the Diffie-Hellman Key Agreement Protocol, when an approved safe prime is used, allows remote attackers (from the client side) to trigger unnecessarily expensive server-side DHE modular-exponentiation calculations. The client may cause asymmetric resource consumption. The basic attack scenario is that the client must claim that it can only communicate with DHE, and the server must be configured to allow DHE and validate the order of the public key.

What

Validating the order of the public keys in the Diffie-Hellman Key Agreement Protocol, when an approved safe prime is used, allows remote attackers (from the client side) to trigger unnecessarily expensive server-side DHE modular-exponentiation calculations. The client may cause asymmetric resource consumption. The basic attack scenario is that the client must claim that it can only communicate with DHE, and the server must be configured to allow DHE and validate the order of the public key.

Why

The product does not validate, or incorrectly validates, a certificate.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Validating the order of the public keys in the Diffie-Hellman Key Agreement Protocol, when an approved safe prime is used, allows remote attackers (from the client side) to trigger unnecessarily expensive server-side DHE modular-exponentiation calculations. The client may cause asymmetric resource consumption. The basic attack scenario is that the client must claim that it can only communicate with DHE, and the server must be configured to allow DHE and validate the order of the public key.

Why

The product does not validate, or incorrectly validates, a certificate.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Certificate Validation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-295 ↗

CWE-295: Improper Certificate Validation. The product does not validate, or incorrectly validates, a certificate.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-295
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2024-3056Diffie-Hellman Implementierungen: Mehrere Schwachstellen ermöglichen Denial of Service

Ein entfernter anonymer Angreifer kann mehrere Schwachstellen in verschiedenen Diffie-Hellman Implementierungen ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240828Security Bulletin 28 Aug 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 28 Aug 2024, published on 28 August 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0627Multiples vulnérabilités dans les produits Splunk

ecord?id=CVE-2024-34156 Référence CVE CVE-2024-34158 https://www.cve.org/CVERecord?id=CVE-2024-34158 Référence CVE CVE-2024-35195 https://www.cve.org/CVERecord?id=CVE-2024-35195 Référence CVE CVE-2024-36114 https://www.cve.org/CVERecord?id=CVE-2024-36114 Référence CVE CVE-2024-3651 https://www.cve.org/CVERecord?id=CVE-2024-3651 Référence CVE CVE-2024-37891 https://www.cve.org/CVERecord?id=CVE-2024-37891 Référence CVE CVE-2024-39689 https://www.cve.org/CVERecord?id=CVE-2024-39689 Référence CVE CVE-2024-4068 https://www.cve.org/CVERecord?id=CVE-2024-4068 Référence CVE CVE-2024-41110 https://www.cve.org/CVERecord?id=CVE-2024-41110 Référence CVE CVE-2024-41996 https://www.cve.org/CVERecord?id=CVE-2024-41996 Référence CVE CVE-2024-45337 https://www.cve.org/CVERecord?id=CVE-2024-45337 Référence CVE CVE-2024-45339 https://www.cve.org/CVERecord?id=CVE-2024-45339 Référence CVE CVE-2024-47081 https://www.cve.org/CVERecord?id=CVE-2024-47081 Référence CVE CVE-2024-47561 https://www.cve.org/CVERecord?id=CVE-2024-47561 Référence CVE CVE-2024-52304 https://www.cve.org/CVERecord?id=CVE-2024-52304 Référence CVE CVE-2024-5321 https://www.cve.org/CVERecord?id=CVE-2024-5321 Référence CVE CVE-2024-53899 https://www.cve.org/CVERecord?id=CVE-2024-53899 Référence CVE CVE-2024-5535 https://www.cve.org/CVERecord?id=CVE

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0266Multiples vulnérabilités dans VMware Tanzu

ecord?id=CVE-2023-32636 Référence CVE CVE-2023-39804 https://www.cve.org/CVERecord?id=CVE-2023-39804 Référence CVE CVE-2023-4156 https://www.cve.org/CVERecord?id=CVE-2023-4156 Référence CVE CVE-2023-45322 https://www.cve.org/CVERecord?id=CVE-2023-45322 Référence CVE CVE-2023-50495 https://www.cve.org/CVERecord?id=CVE-2023-50495 Référence CVE CVE-2024-0232 https://www.cve.org/CVERecord?id=CVE-2024-0232 Référence CVE CVE-2024-11053 https://www.cve.org/CVERecord?id=CVE-2024-11053 Référence CVE CVE-2024-13176 https://www.cve.org/CVERecord?id=CVE-2024-13176 Référence CVE CVE-2024-34459 https://www.cve.org/CVERecord?id=CVE-2024-34459 Référence CVE CVE-2024-41996 https://www.cve.org/CVERecord?id=CVE-2024-41996 Référence CVE CVE-2024-7264 https://www.cve.org/CVERecord?id=CVE-2024-7264 Référence CVE CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-9681 Référence CVE CVE-2025-13151 https://www.cve.org/CVERecord?id=CVE-2025-13151 Référence CVE CVE-2025-14017 https://www.cve.org/CVERecord?id=CVE-2025-14017 Référence CVE CVE-2025-14087 https://www.cve.org/CVERecord?id=CVE-2025-14087 Référence CVE CVE-2025-14512 https://www.cve.org/CVERecord?id=CVE-2025-14512 Référence CVE CVE-2025-14831 https://www.cve.org/CVERecord?id=CVE-2025-14831 Référence CVE CVE-2025-15281 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0101Multiples vulnérabilités dans les produits Siemens

ord?id=CVE-2022-48174 Référence CVE CVE-2023-39810 https://www.cve.org/CVERecord?id=CVE-2023-39810 Référence CVE CVE-2023-42363 https://www.cve.org/CVERecord?id=CVE-2023-42363 Référence CVE CVE-2023-42364 https://www.cve.org/CVERecord?id=CVE-2023-42364 Référence CVE CVE-2023-42365 https://www.cve.org/CVERecord?id=CVE-2023-42365 Référence CVE CVE-2023-42366 https://www.cve.org/CVERecord?id=CVE-2023-42366 Référence CVE CVE-2023-7256 https://www.cve.org/CVERecord?id=CVE-2023-7256 Référence CVE CVE-2024-11053 https://www.cve.org/CVERecord?id=CVE-2024-11053 Référence CVE CVE-2024-12718 https://www.cve.org/CVERecord?id=CVE-2024-12718 Référence CVE CVE-2024-41996 https://www.cve.org/CVERecord?id=CVE-2024-41996 Référence CVE CVE-2024-47619 https://www.cve.org/CVERecord?id=CVE-2024-47619 Référence CVE CVE-2024-52533 https://www.cve.org/CVERecord?id=CVE-2024-52533 Référence CVE CVE-2024-6197 https://www.cve.org/CVERecord?id=CVE-2024-6197 Référence CVE CVE-2024-6874 https://www.cve.org/CVERecord?id=CVE-2024-6874 Référence CVE CVE-2024-7264 https://www.cve.org/CVERecord?id=CVE-2024-7264 Référence CVE CVE-2024-8006 https://www.cve.org/CVERecord?id=CVE-2024-8006 Référence CVE CVE-2024-8096 https://www.cve.org/CVERecord?id=CVE-2024-8096 Référence CVE CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-96

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0524Multiples vulnérabilités dans VMware Tanzu

ecord?id=CVE-2024-34156 Référence CVE CVE-2024-34158 https://www.cve.org/CVERecord?id=CVE-2024-34158 Référence CVE CVE-2024-34402 https://www.cve.org/CVERecord?id=CVE-2024-34402 Référence CVE CVE-2024-34403 https://www.cve.org/CVERecord?id=CVE-2024-34403 Référence CVE CVE-2024-35195 https://www.cve.org/CVERecord?id=CVE-2024-35195 Référence CVE CVE-2024-3596 https://www.cve.org/CVERecord?id=CVE-2024-3596 Référence CVE CVE-2024-3651 https://www.cve.org/CVERecord?id=CVE-2024-3651 Référence CVE CVE-2024-38949 https://www.cve.org/CVERecord?id=CVE-2024-38949 Référence CVE CVE-2024-38950 https://www.cve.org/CVERecord?id=CVE-2024-38950 Référence CVE CVE-2024-41996 https://www.cve.org/CVERecord?id=CVE-2024-41996 Référence CVE CVE-2024-45336 https://www.cve.org/CVERecord?id=CVE-2024-45336 Référence CVE CVE-2024-45341 https://www.cve.org/CVERecord?id=CVE-2024-45341 Référence CVE CVE-2024-45993 https://www.cve.org/CVERecord?id=CVE-2024-45993 Référence CVE CVE-2024-4603 https://www.cve.org/CVERecord?id=CVE-2024-4603 Référence CVE CVE-2024-46981 https://www.cve.org/CVERecord?id=CVE-2024-46981 Référence CVE CVE-2024-4741 https://www.cve.org/CVERecord?id=CVE-2024-4741 Référence CVE CVE-2024-49203 https://www.cve.org/CVERecord?id=CVE-2024-49203 Référence CVE CVE-2024-5171 https://www.cve.org/CVERecord?id=CVE-2

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-030389Diffie-Hellman鍵交換におけるサービス運用妨害（DoS）の脆弱性

Diffie-Hellman鍵交換には、サービス運用妨害（DoS）の脆弱性が存在します。 CVE-2002-20001 ：本脆弱性は2021年11月に公開されたものです。 CVE-2022-40735 ：本脆弱性は2022年11月に公開されたものです。 CVE-2024-41996 ：本脆弱性は2024年8月に公開されたものです。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0079Kwetsbaarheden verholpen in Siemens producten

A vulnerability in the Diffie-Hellman Key Agreement Protocol in OpenSSL allows remote attackers to cause excessive server-side computational load by exploiting public key order validation with approved safe primes, addressed in updates fixing CVE-2023-50782 and CVE-2024-41996.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Update to V4.0.800 or later version
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 26 Aug 2024 · Last source change 12 May 2026, 11:56 UTC · CWE-295 · Improper Certificate Validation

CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-39313
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
NVD statusNVD not scheduled

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    n/a · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    n/a · Fixed: Update to V4.0.800 or later version
    Siemens ProductCERT ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Siemens ProductCERT ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2024-39313↗Vendor CSAF · SUSE Product Security Team↗Siemens ProductCERT security advisory · Siemens SSA-485750↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-41996 · cve.blacktree.nl