Cyber Resilience

CVE-2024-42512

Opcfoundation Ua .Net Standard Stack ≤ 1.5.374.158

Published
10 February 2025
Modified
29 September 2025
Patch / advisory
CVSS Score v3.1 8.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
EPSS Score 0.0058 45th percentile
Risk Priority 65 floored blend · peak EPSS

Summary

CVE-2024-42512 is a high-severity Observable Timing Discrepancy (CWE-208) vulnerability in Opcfoundation Ua .Net Standard Stack. Its CVSS base score is 8.6 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Password Guessing (T1110.001); ranked at the 45th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-42512 is a vulnerability in the OPC UA .NET Standard Stack prior to version 1.5.374.158. It allows an unauthorized attacker to bypass application authentication when the deprecated Basic128Rsa15 security policy is enabled. The issue is classified under CWE-208 (Observable Timing Discrepancy) and carries a CVSS v3.1 base score of 8.6 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L), indicating high severity due to its network accessibility and potential for significant confidentiality impact.

The vulnerability can be exploited by any unauthorized attacker with network access to the affected component, requiring low attack complexity and no privileges, user interaction, or special conditions beyond the Basic128Rsa15 policy being enabled. Successful exploitation enables authentication bypass, granting unauthorized access that could result in high confidentiality loss, such as exposure of sensitive data, alongside low impacts to integrity and availability.

Mitigation details are provided in the OPC Foundation Security Bulletin available at https://files.opcfoundation.org/SecurityBulletins/OPC%20Foundation%20Security%20Bulletin%20CVE-2024-42512.pdf, published on 2025-02-10.

EU & UK References

Vulnerability Data

Vulnerability in the OPC UA .NET Standard Stack before 1.5.374.158 allows an unauthorized attacker to bypass application authentication when the deprecated Basic128Rsa15 security policy is enabled.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1110.001 Password Guessing Credential Access
Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.
T1087 Account Discovery Discovery
Adversaries may attempt to get a listing of valid accounts, usernames, or email addresses on a system or within a compromised environment.
T1087.001 Local Account Discovery
Adversaries may attempt to get a listing of local system accounts.
T1087.002 Domain Account Discovery
Adversaries may attempt to get a listing of domain accounts.
T1087.003 Email Account Discovery
Adversaries may attempt to get a listing of email addresses and accounts.
T1087.004 Cloud Account Discovery
Adversaries may attempt to get a listing of cloud accounts.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-42513Same product: Opcfoundation Ua .Net Standard Stack
CVE-2026-23892Shared CWE-208
CVE-2026-40263Shared CWE-208
CVE-2026-43606Shared CWE-208
CVE-2024-41828Shared CWE-208
CVE-2026-40972Shared CWE-208
CVE-2026-5086Shared CWE-208
CVE-2026-13758Shared CWE-208
CVE-2024-52307Shared CWE-208
CVE-2025-59350Shared CWE-208

Affected Assets

opcfoundation
ua .net standard stack
≤ 1.5.374.158

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V11.2.4

Mitigating Controls (NIST 800-53 r5) AI

Developer testing can include timing analysis or side-channel test cases that reveal observable timing discrepancies.

Engineering principles can mandate constant-time algorithms and side-channel resistance so timing discrepancies are never introduced.

Requiring approved cryptographic modules and algorithms implicitly demands implementations free of observable timing leaks.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require constant-time implementations that eliminate observable timing discrepancies.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

none

Consistent reference clocks limit the attacker's ability to measure or manipulate timing differences that could reveal internal state or processing paths.

References