dbcve.org
Tnc 640 Programming StationApplication · Heidenhain

CVE-2022-41648

CRITICAL · 9.8 CVSS v3.1 Published 2022-10-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
The HEIDENHAIN Controller TNC 640 NC software Version 340590 07 SP5, is vulnerable to improper authentication in its DNC communication for CNC machines. Authentication is not enabled by default for DNC communication. This vulnerability may allow an attacker to deny service on the production line, steal sensitive data from the production line, and alter any products created by the production line. Note: CNC machines running the TNC 640 controller require DNC to be enabled for DNC communication to be present.

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 confidence

The HEIDENHAIN TNC 640 controller running NC software Version 340590 07 SP5 has improper authentication in its DNC (Distributed Numerical Control) communication feature. Authentication is not enabled by default for DNC communication, allowing unauthenticated network attackers to potentially disrupt CNC machine operations, exfiltrate sensitive production data, or manipulate manufactured products.

MitigationEnable authentication for DNC communication on affected TNC 640 controllers; this requires configuration changes via the controller's DNC settings and verifying authenticated connectivity without disrupting production workflows.

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
Tnc 640 Programming StationApplication
Affected:= 340590_07
HerosOperating system
Affected:= 5.08.3

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
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 checks

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

  1. Identify the installed TNC 640 NC software version
    Access the controller's system information or version display (typically via the Settings > Version or Help > Info menu path on the TNC interface). Record the full version string including the build number.
    Affected if The installed version matches 340590_07 (Programming Station) or 5.08.3 (Heros).
  2. Locate the DNC communication settings
    Navigate to the controller's DNC configuration panel. This is typically found under Settings > DNC or Settings > Interfaces > DNC on the TNC 640 interface. Note the current configuration state.
    Affected if DNC communication is enabled or configured on the controller.
  3. Verify DNC authentication status
    Within the DNC settings panel, locate the authentication or security options for DNC communication. Check whether authentication is currently enabled or disabled for inbound DNC connections.
    Affected if Authentication is shown as disabled or not configured for DNC communication.
  4. Identify the DNC network listening port
    Check the DNC configuration for the TCP/UDP port number used for DNC communication (common default is port 19000). Document the interface binding (e.g., all interfaces vs. specific IP).
    Affected if DNC is bound to a network-accessible interface and is accepting connections without authentication.

If the installed version is 340590_07 or 5.08.3, DNC communication is enabled, and authentication is disabled for DNC, the environment is affected by CVE-2022-41648.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable authentication for DNC communication on affected TNC 640 controllers; this requires configuration changes via the controller's DNC settings and verifying authenticated connectivity without disrupting production workflows.

Fix this in Tnc 640 Programming Station Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41648 — 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-2022-41648 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