CVE-2024-42513
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVulnerability in the OPC UA .NET Standard Stack before 1.5.374.158 allows an unauthorized attacker to bypass application authentication when using HTTPS endpoints.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe OPC UA .NET Standard Stack before version 1.5.374.158 contains an authentication bypass vulnerability specific to HTTPS endpoints. An attacker can bypass application authentication mechanisms when connecting via HTTPS, potentially allowing unauthorized access to OPC UA services.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.5.374.158CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the OPC UA .NET Standard Stack assemblyFind the Opc.Ua.Core.dll or Opc.Ua.Bindings.dll assembly in your application deployment or reference the NuGet package version used in your project. Use PowerShell: Get-ItemProperty -Path 'path\to\Opc.Ua.Core.dll' | Select-Object VersionInfo or check the package reference in your .csproj file.Affected if The assembly version or NuGet package version is below 1.5.374.158
-
Identify if HTTPS endpoints are configuredReview your application configuration files (for example, appsettings.json, Opc.Ua.Server.Config.xml, or custom .config files) for HTTPS binding settings, server certificate configuration, or endpoint URLs using the https:// scheme.Affected if HTTPS endpoints are enabled or configured in your OPC UA server settings
-
Check if application authentication is enforcedExamine your endpoint configuration for authentication settings. Look for SecurityPolicy, MessageSecurityMode, and UserTokenPolicy configurations. Verify whether ApplicationAuthentication or UserAuthentication is explicitly set.Affected if Application-level authentication is configured as the authentication mechanism for the HTTPS endpoint
-
Verify authentication bypass riskIf both conditions above are true (version < 1.5.374.158 AND HTTPS endpoints are used with application authentication), the environment is vulnerable. The vulnerability allows bypass of application authentication specifically on HTTPS endpoints.Affected if Running a version below 1.5.374.158 with HTTPS endpoints enabled and application authentication configured
Your environment is affected if you are using a version of the OPC UA .NET Standard Stack prior to 1.5.374.158 with HTTPS endpoints enabled and relying on application authentication mechanisms.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.5.374.158
Upgrade the OPC UA .NET Standard Stack to version 1.5.374.158 or later. Verify that application authentication is properly enforced on all HTTPS endpoints after the update.
1.5.374.158
- 1. Identify the current version of OPC UA .NET Standard Stack in use within your application or system
- 2. Navigate to the official OPC Foundation repository at files.opcfoundation.org
- 3. Download OPC UA .NET Standard Stack version 1.5.374.158 or a later stable release
- 4. Replace the existing OPC UA .NET Standard Stack binaries with the fixed version
- 5. Rebuild and redeploy your application if using the stack as a library
- 6. Verify that HTTPS endpoints now properly enforce application authentication
- 7. Confirm the vulnerability is resolved by testing with unauthorized credentials
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-42513 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-42513 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data