CVE-2024-8448
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 · uneditedCertain switch models from PLANET Technology have a hard-coded credential in the specific command-line interface, allowing remote attackers with regular privilege to log in with this credential and obtain a Linux root shell.
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 confidencePLANET Technology network switches contain a hardcoded credential embedded in the CLI firmware. An authenticated attacker with regular user privileges can use this hidden credential to bypass authentication controls and spawn a Linux root shell, achieving full device compromise.
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.305b240719CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 device model and firmware versionAccess the CLI or web interface of the switch and run 'show version' or check the system information page to confirm the exact model (Gs 4210 24p2s or Gs 4210 24pl4c) and firmware version installedAffected if The device is a Planet Gs 4210 24p2s with firmware < 3.305b240802 or a Planet Gs 4210 24pl4c with firmware < 2.305b240719
-
Verify CLI service statusCheck if the command-line interface service is enabled and accessible on the switch (typically via telnet or SSH on management ports)Affected if CLI access is enabled and reachable from any network segment
-
Check for unauthorized access indicatorsReview system logs for authentication attempts using non-standard credentials or successful logins from unexpected sourcesAffected if Multiple failed authentication attempts precede successful root-level access, or unexpected admin accounts appear in the system
The environment is affected if the device is a Planet Gs 4210 24p2s running firmware below 3.305b240802 or a Planet Gs 4210 24pl4c running firmware below 2.305b240719, and the CLI interface is accessible to untrusted users.
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
Apply vendor firmware updates to remove the hardcoded credential; if unavailable, restrict CLI access to trusted management networks and disable unnecessary remote access protocols.
Firmware >= 3.305b240802 (Gs 4210 24p2s) or >= 2.305b240719 (Gs 4210 24pl4c)
- 1. Identify the exact model of the PLANET switch (Gs 4210 24p2s or Gs 4210 24pl4c)
- 2. Check the current firmware version on the device through the CLI or web interface
- 3. Navigate to PLANET Technology's official support/download website
- 4. Locate and download the fixed firmware version: >= 3.305b240802 for Gs 4210 24p2s, or >= 2.305b240719 for Gs 4210 24pl4c
- 5. Follow PLANET's documented firmware upgrade procedure (typically via web UI, TFTP, or console)
- 6. After upgrade, verify the new firmware version is running and confirm the hard-coded credential is no longer present
- 7. Change any passwords that may have been exposed during the vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8448 — 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-8448 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