CVE-2023-3935
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 · uneditedA heap buffer overflow vulnerability in Wibu CodeMeter Runtime network service up to version 7.60b allows an unauthenticated, remote attacker to achieve RCE and gain full access of the host system.
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 · moderate confidenceA heap buffer overflow vulnerability in the Wibu CodeMeter Runtime network service (versions up to 7.60b) allows an unauthenticated remote attacker to execute arbitrary code and gain full control of the host system due to insufficient bounds checking in the network communication handler.
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< 7.60c>= 1.0.0, <= 3.0.22>= 1.0.1, <= 4.6.3>= 18.02.r8, <= 23.06.01= 05.03.00.00>= 14.00, <= 22.00.00>= 1.5.2, <= 1.11.1>= 08.00, <= 12.01.00.00CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify if Wibu CodeMeter Runtime is installedCheck for the presence of CodeMeter Runtime software on the system. This may be listed in installed programs (Windows), package managers (Linux), or running services.Affected if CodeMeter Runtime is present on the system.
-
Determine the installed version of CodeMeter RuntimeLocate and read the version information of the installed CodeMeter Runtime. Compare the version number against the affected range: versions less than 7.60c are vulnerable.Affected if The installed version is lower than 7.60c (for example, 7.60b or earlier).
-
Verify if the CodeMeter network service is runningCheck if the CodeMeter Runtime network service (Cm Wan Server or similar network service component) is actively running and listening on network ports.Affected if The network service component is running and accepting connections.
-
Assess network exposure of the CodeMeter serviceDetermine whether the CodeMeter network service port is exposed to untrusted networks or accessible from outside the local host.Affected if The service is reachable from network segments that contain untrusted or unknown users, making remote exploitation possible.
A system is affected if it runs Wibu CodeMeter Runtime version lower than 7.60c (or any of the listed Trumpf products within their affected version ranges) with the network service enabled and accessible to untrusted network access.
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 · scoped7.60c
Upgrade Wibu CodeMeter Runtime to a version newer than 7.60b; if immediate patching is not feasible, implement network segmentation to restrict unauthorized access to the CodeMeter service port from untrusted networks.
CodeMeter Runtime 7.60c or later
- Upgrade CodeMeter Runtime to version 7.60c or later
- For products bundled with CodeMeter Runtime (Oseon, Programmingtube, Teczonebend, Tops Unfold, Topscalculation, Trumpflicenseexpert, Trutops), ensure the underlying CodeMeter Runtime component is updated to 7.60c or newer
- Verify the installed version matches or exceeds the fixed release
- Restart CodeMeter Runtime service after upgrade to ensure changes take effect
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3935 — 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-2023-3935 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