cve.bz

CVE-2020-14517 wibu codemeter: Inadequate Encryption Strength

9.8 criticalEPSS 0.7%

Critical (9.8) in wibu codemeter. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
Protocol encryption can be easily broken for CodeMeter (All versions prior to 6.90 are affected, including Version 6.90 or newer only if CodeMeter Runtime is running as server) and the server accepts external connections, which may allow an attacker to remotely communicate with the CodeMeter API.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 53rd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-327 Use of a Broken or Risky Cryptographic Algorithm
CWE-326 Inadequate Encryption Strength
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2020-14517 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-14517?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-14517?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-14517 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
wibu:codemeterbefore 6.90

ICS advisories (CISA)

AdvisoryTitlePublishedSectorsAffectedFixed
ICSA-26-076-01CODESYS in Festo Automation Suite2026-02-26Critical ManufacturingFesto Automation Suite <2.8.0.138 installed with CODESYS Development System 3.0, Festo Automation Suite <2.8.0.138 installed with CODESYS Development System 3.5.16.10, Festo Automation Suite 2.8.0.137 installed with CODESYS Development System 3.0 and 1 moreCODESYS Development System 3.5.21.20 external component of Festo Automation Suite 2.8.0.138
ICSA-20-203-01Wibu-Systems CodeMeter (Update F)2020-08-20MultipleCodeMeter: All versions prior to 7.10a are affected by CVE-2020-14509 and CVE-2020-14519, CodeMeter: All versions prior to 6.90 are affected by CVE-2020-14515 when using CmActLicense update files with CmActLicense Firm Code, CodeMeter: All versions prior to 7.10a are affected by CVE-2020-14517 and 2 morenone listed

From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.

Attack patterns (CAPEC)

  • CAPEC-20 Encryption Brute Forcing Likelihood: Low · Severity: Low
  • CAPEC-112 Brute Force Severity: High
  • CAPEC-192 Protocol Analysis Likelihood: Low · Severity: Low
  • CAPEC-97 Cryptanalysis Likelihood: Low · Severity: Very High
  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-473 Signature Spoof
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High
  • CAPEC-608 Cryptanalysis of Cellular Encryption Severity: High
  • CAPEC-614 Rooting SIM Cards Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON