CVE-2022-29897
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 · uneditedOn various RAD-ISM-900-EN-* devices by PHOENIX CONTACT an admin user could use the traceroute utility integrated in the WebUI to execute arbitrary code with root privileges on the OS due to an improper input validation in all versions of the firmware.
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 confidenceThis is a command injection vulnerability in the traceroute utility within the WebUI of Phoenix Contact RAD-ISM-900-EN-* industrial wireless devices. An authenticated administrator can inject arbitrary OS commands through improper input validation in the traceroute parameter, achieving root-level code execution on the underlying Linux system.
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 dataall versionsall versionsall versionsCVSS 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 modelAccess the device WebUI or check the device label/hostname to confirm it is a Phoenix Contact RAD-ISM-900-EN-* series device (such as RAD-ISM-900-EN-BD, RAD-ISM-900-EN-BD/B, or RAD-ISM-900-EN-BD-BUS)Affected if The device is any Phoenix Contact RAD-ISM-900-EN-* variant
-
Confirm WebUI accessibilityAttempt to reach the device management interface via HTTP/HTTPS on the expected management IP address. The traceroute vulnerability exists within the WebUI, not through other interfacesAffected if The WebUI is accessible over the network
-
Verify administrative accessCheck if valid administrator credentials can be obtained or are configured for the WebUI. The vulnerability requires an authenticated administrator sessionAffected if Administrative credentials exist or can be obtained for the WebUI
-
Locate traceroute functionalityLog into the WebUI and navigate through the administrative interface to find the traceroute utility. This is typically found under network diagnostics or tools menusAffected if The traceroute feature is present and accessible in the WebUI (all versions contain this feature)
-
Check firmware versionIn the WebUI, look for a firmware version or software information page, usually under System, Status, or About sectionsAffected if The firmware version displayed matches any RAD-ISM-900-EN-* variant (all versions are affected)
If the device is a Phoenix Contact RAD-ISM-900-EN-* series unit with an accessible WebUI and administrative credentials are available, the environment is affected since all firmware versions contain the vulnerable traceroute command injection flaw.
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 dataApply any available vendor firmware updates; until patched, restrict administrative access to trusted users only and consider network segmentation to limit exposure of the web management interface.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29897 — 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-2022-29897 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