dbcve.org
CodemeterApplication · Wibu

CVE-2020-14519

HIGH · 7.5 CVSS v3.1 Published 2020-09-16
Fix available
A fix is available. Upgrade to 7.00 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
This vulnerability allows an attacker to use the internal WebSockets API for CodeMeter (All versions prior to 7.00 are affected, including Version 7.0 or newer with the affected WebSockets API still enabled. This is especially relevant for systems or devices where a web browser is used to access a web server) via a specifically crafted Java Script payload, which may allow alteration or creation of license files for when combined with CVE-2020-14515.

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 confidence

The vulnerability exists in the internal WebSockets API of CodeMeter (versions prior to 7.00, or version 7.0+ with WebSockets API still enabled). Attackers can exploit this by sending specifically crafted JavaScript payloads through the WebSockets connection. When chained with CVE-2020-14515, this allows alteration or creation of license files, posing a significant risk in environments where web browsers access web servers connected to CodeMeter.

MitigationUpgrade to CodeMeter version 7.00 or later, or disable the affected WebSockets API if upgrading is not feasible. This is especially critical for systems where browsers can access web servers running CodeMeter.

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
CodemeterApplication
Affected:< 7.00

CVSS 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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify CodeMeter version
    Locate and inspect the installed CodeMeter software to determine its version number. This is typically found in the program's 'About' information, the installed files, or via the CodeMeter Control Center interface.
    Affected if The installed version is less than 7.00 (for example, 6.x or earlier)
  2. Verify WebSockets API status on version 7.0+
    If the installed version is 7.0 or higher, examine the CodeMeter configuration settings to determine whether the internal WebSockets API remains enabled.
    Affected if Version is 7.0 or higher AND the WebSockets API is still enabled in the configuration
  3. Confirm CodeMeter service is running
    Verify that the CodeMeter service daemon is actively running on the system, as the vulnerability requires the service to be operational for exploitation.
    Affected if The CodeMeter service is running and accessible on the host
  4. Assess network exposure
    Determine whether the system running CodeMeter can be reached by untrusted web browsers, particularly from external or less trusted network segments.
    Affected if Web browsers can access web servers connected to the CodeMeter instance (the service is network-accessible to browsers)
  5. Check for related CVE-2020-14515
    Review the environment for the presence of CVE-2020-14515, as this vulnerability is often chained with it to achieve license file alteration.
    Affected if CVE-2020-14515 is also present in the same environment

You are affected if CodeMeter version is below 7.00, OR version 7.0+ has the WebSockets API enabled and is accessible to web browsers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to 7.00 or later
Fixed in 7.00
Interim mitigation

Upgrade to CodeMeter version 7.00 or later, or disable the affected WebSockets API if upgrading is not feasible. This is especially critical for systems where browsers can access web servers running CodeMeter.

Fix this in Codemeter Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-14519 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-14519 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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