CVE-2024-6422
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 · uneditedAn unauthenticated remote attacker can manipulate the device via Telnet, stop processes, read, delete and change data.
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 critical unauthenticated remote code execution vulnerability in network devices allowing attackers to manipulate the device via Telnet, stop processes, and perform arbitrary read/write/delete operations on data without any credentials.
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<= 2.11.0<= 2.11.0<= 2.11.0<= 2.11.0CVSS 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 the device modelCheck the device label or system information to confirm it is a Pepperl Fuchs Oit700, Oit500, Oit200, or Oit1500 with the F113 B12 Cb variant.Affected if The device is not one of these four models, then it is not affected by this CVE.
-
Determine the installed firmware versionAccess the device management interface or use the vendor-supplied diagnostic tool to retrieve the firmware version. Compare it against the affected range.Affected if Firmware version is 2.11.0 or lower, the device is within the affected version range.
-
Verify Telnet service statusCheck the device configuration or network settings to determine if Telnet access is enabled. This can be done by reviewing the device web interface, command-line interface, or configuration files.Affected if Telnet is enabled and accessible on the device, the vulnerability is exploitable since the attack vector requires Telnet.
-
Confirm network accessibility of Telnet portPerform a port scan or connectivity test from an external system to verify whether TCP port 23 (Telnet) is open and reachable on the device.Affected if Port 23 is open and reachable from untrusted networks, the device is exposed to remote exploitation.
The device is affected if it is a Pepperl Fuchs Oit700, Oit500, Oit200, or Oit1500 (F113 B12 Cb) running firmware version 2.11.0 or lower with Telnet service enabled and accessible.
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.
From vendor dataImmediately disable Telnet access on affected devices, implement network segmentation or firewall rules to restrict Telnet to trusted management networks, and apply vendor patches if available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6422 — 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-2024-6422 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