CVE-2024-36445
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 · uneditedSwissphone DiCal-RED 4009 devices allow a remote attacker to gain a root shell via TELNET without authentication.
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 confidenceUnauthenticated remote code execution vulnerability in Swissphone DiCal-RED 4009 devices allows remote attackers to gain root shell access via TELNET without any credentials. The exposed TELNET service accepts connections from the network and provides direct root shell access, making this a critical pre-auth RCE with network-level exploitability.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the device label, web interface, or system information to confirm the model is Swissphone DiCal-RED 4009Affected if The device is a Swissphone DiCal-RED 4009 unit
-
Detect if TELNET service is enabledRun 'netstat -tlnp' or 'ss -tlnp' on the device to check if port 23 (TELNET) is listeningAffected if Port 23 is open and listening on the device
-
Check if TELNET allows unauthenticated root accessConnect to the device's TELNET port (e.g., using 'telnet <device_ip>' or 'nc <device_ip> 23') and observe if a root shell prompt appears without providing credentialsAffected if Connecting to TELNET provides a root shell without requiring any username or password
-
Assess network exposure of TELNET portFrom an external system, run 'nmap -p 23 <device_ip>' or 'nc -zv <device_ip> 23' to check if port 23 is accessible from the networkAffected if Port 23 is reachable from untrusted network segments
If the device is a Swissphone DiCal-RED 4009 with TELNET port 23 open and accessible, and TELNET grants root shell access without authentication, the environment is affected by this CVE.
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 the TELNET service if not business-critical, or restrict access to TELNET port (23) via firewall/network segmentation to prevent unauthorized external access. Contact Swissphone for firmware updates if available.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36445 — 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-36445 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