CVE-2024-8455
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 · uneditedThe swctrl service is used to detect and remotely manage PLANET Technology devices. For certain switch models, the authentication tokens used during communication with this service are encoded user passwords. Due to insufficient strength, unauthorized remote attackers who intercept the packets can directly crack them to obtain plaintext passwords.
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 confidenceThe swctrl service on PLANET Technology switches uses weak encoding (not proper encryption or hashing) for authentication tokens that are derived from user passwords. Attackers on the network can intercept these encoded tokens and easily decode them to recover plaintext 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< 3.305b240802< 2.305b240719all 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
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 switch modelLog into the switch CLI or web interface and retrieve the model number from the system information (typically via 'show system-info' command or the web dashboard)Affected if The model is one of: Planet Gs 4210 24p2s, Planet Gs 4210 24pl4c, or Planet Igs 5225 4up1t2s
-
Check firmware versionRetrieve the firmware version from the switch (via 'show version' CLI command or web interface firmware status). Compare your installed version to the affected ranges: Gs 4210 24p2s is affected if version < 3.305b240802, Gs 4210 24pl4c is affected if version < 2.305b240719, and Igs 5225 4up1t2s is affected for all versionsAffected if The firmware version falls within the affected range for your model, or you have an Igs 5225 4up1t2s model at any version
-
Verify swctrl service statusCheck if the swctrl service is enabled on the switch. This is typically configured in the switch settings or can be queried via SNMP, or check for processes listening on the swctrl service port (commonly port 8000 or 8080 for PLANET switches)Affected if The swctrl service is running and listening on a network interface
-
Check network accessibility of swctrlFrom a system on the same network, attempt to reach the swctrl service port on the switch (for example, using netcat or telnet to connect to the switch IP on common swctrl ports). Verify if the service is exposed without TLS encryptionAffected if The swctrl service is accessible over the network without TLS encryption (HTTP instead of HTTPS, or unencrypted protocol)
-
Inspect authentication token formatIf you can capture or observe network traffic to/from the swctrl service (using a packet capture tool), examine the authentication tokens. Look for tokens that use simple base64 encoding or similar weak encoding rather than cryptographic hashingAffected if Authentication tokens are encoded using weak encoding (such as base64) rather than proper cryptographic hashing or encryption
Your switch is affected if it is a Planet Gs 4210 24p2s, Gs 4210 24pl4c, or Igs 5225 4up1t2s model running a firmware version within the affected ranges, with the swctrl service enabled and accessible over the network using weak token encoding.
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.
dbcve · scoped2.305b2407193.305b240802
Replace the weak password encoding with strong cryptographic hashing or encryption, enforce TLS for all swctrl service communications, and rotate any credentials that may have been compromised.
Gs 4210 24p2s: firmware >= 3.305b240802; Gs 4210 24pl4c: firmware >= 2.305b240719; Igs 5225 4up1t2s: no fixed version listed in provided material
- Identify the exact model of the affected PLANET Technology switch (Gs 4210 24p2s, Gs 4210 24pl4c, or Igs 5225 4up1t2s)
- Download the appropriate fixed firmware version from PLANET Technology's official support website: For Gs 4210 24p2s use version 3.305b240802 or later, for Gs 4210 24pl4c use version 2.305b240719 or later
- Access the switch management interface via web browser or console
- Navigate to the Firmware Upgrade section in the administrative interface
- Upload and apply the downloaded firmware file
- Verify the upgrade was successful by checking the firmware version in the device status
- Restart the device if prompted to complete the installation
- After upgrade, verify that the swctrl service now uses proper authentication mechanisms instead of weak encoding
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8455 — 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-8455 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