CVE-2024-22809VulnerabilityPublished 22 Apr 2024Updated 1 Aug 2024

CVE-2024-22809: n/a

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-22809, organizations should implement strict network segmentation and access controls to limit exposure of the PathPilot Controller to trusted networks only. Use firewalls or VLANs to isolate CNC controllers from general corporate or internet-facing networks. Employ strong monitoring and logging of file access to detect unauthorized attempts to view the G code shared folder. If possible, disable or restrict SMB or other file sharing protocols used by the controller to share G code files. Regularly audit user and device permissions to ensure no unintended access paths exist. Until an official patch or update is released by Tormach, consider manual review and restriction of shared folder permissions on the controller. Engage with the vendor for updates and apply patches promptly once available. Additionally, educate staff on the sensitivity of G code files and enforce policies to prevent unauthorized copying or transmission.

Description

Incorrect access control in Tormach xsTECH CNC Router, PathPilot Controller v2.9.6 allows attackers to access the G code's shared folder and view sensitive information.

Impact

The primary impact of CVE-2024-22809 is the unauthorized disclosure of sensitive G code files, which contain detailed instructions for CNC machining processes. Exposure of these files can lead to intellectual property theft, loss of competitive advantage, and potential sabotage if attackers analyze or replicate manufacturing processes. While the vulnerability does not allow modification or disruption of the CNC operations, the confidentiality breach alone can have significant financial and reputational consequences for affected organizations. Industrial manufacturers relying on Tormach xsTECH CNC Routers are at risk, especially those producing proprietary or sensitive components. The lack of required privileges or user interaction lowers the barrier for exploitation, increasing the likelihood of unauthorized access if network controls are insufficient. The absence of known exploits reduces immediate risk but does not eliminate the threat, as attackers may develop exploits over time.

CWE-228Improper Handling of Syntactically Invalid Structure (opens in a new tab)
Class weakness
The product does not handle or incorrectly handles input that is not syntactically well-formed with respect to the associated specification.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

gist.github.com/VcuCyber/51075894d1728db07fc2df286c003df9 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 10:10 UTC

WeaknessesCWE-228

Technical details

References

Community reviews

Related threats