dbcve.org
Gs 4210 24p2s FirmwareOperating system · Planet

CVE-2024-8449

MEDIUM · 6.8 CVSS v3.1 Published 2024-09-30
Fix available
A fix is available. Upgrade to 2.305b240719 / 3.305b240802 or later.
See remediation →
73/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
Certain switch models from PLANET Technology have a Hard-coded Credential in the password recovering functionality, allowing an unauthenticated attacker to connect to the device via the serial console and use this credential to reset any user's password.

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 confidence

Certain PLANET Technology switch models contain a hard-coded credential embedded in the password recovery functionality. An unauthenticated attacker with physical access to the device's serial console can exploit this credential to reset any user's password, gaining full administrative access.

MitigationApply vendor-supplied firmware patches when available; until then, restrict physical access to serial console ports and monitor for unauthorized physical access attempts.

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
Gs 4210 24p2s FirmwareOperating system
Affected:< 3.305b240802
Gs 4210 24pl4c FirmwareOperating system
Affected:< 2.305b240719

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
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access the switch CLI or web interface and retrieve the exact model number. Compare against affected models: Planet Gs 4210 24p2s and Planet Gs 4210 24pl4c.
    Affected if Device model is either Gs 4210 24p2s or Gs 4210 24pl4c.
  2. Check installed firmware version
    Execute the command to display firmware version (typically via 'show version' or similar CLI command). Compare the installed version against the affected ranges: Gs 4210 24p2s is vulnerable if version is earlier than 3.305b240802; Gs 4210 24pl4c is vulnerable if version is earlier than 2.305b240719.
    Affected if Firmware version is below 3.305b240802 for Gs 4210 24p2s, or below 2.305b240719 for Gs 4210 24pl4c.
  3. Verify serial console accessibility
    Inspect the physical location and configuration of the device's serial console port. Determine if the serial port is exposed or reachable by unauthorized personnel.
    Affected if Serial console port is physically accessible to unauthorized individuals.
  4. Inspect password recovery functionality
    Access the device's password recovery mechanism via serial console. Examine whether a hard-coded credential is present that can reset any user password without authentication.
    Affected if A hard-coded credential exists in the password recovery function that allows bypassing authentication.

A user is affected if they have a Gs 4210 24p2s or Gs 4210 24pl4c switch running firmware below the specified version thresholds and the serial console is accessible, allowing exploitation of the hard-coded credential in password recovery.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.305b240719 / 3.305b240802 or later
Fixed in 2.305b2407193.305b240802
Interim mitigation

Apply vendor-supplied firmware patches when available; until then, restrict physical access to serial console ports and monitor for unauthorized physical access attempts.

Recommended fix High confidence

Firmware 3.305b240802 (Gs 4210 24p2s) and Firmware 2.305b240719 (Gs 4210 24pl4c) or later

  1. Identify the exact model of the affected PLANET switch (Gs 4210 24p2s or Gs 4210 24pl4c)
  2. Check the current firmware version via the device management interface or serial console
  3. Download the appropriate firmware version from PLANET Technology's official support page: upgrade to firmware version 3.305b240802 or later for Gs 4210 24p2s, or version 2.305b240719 or later for Gs 4210 24pl4c
  4. Follow PLANET's standard firmware upgrade procedure, typically via web UI (Maintenance > Firmware Upgrade) or TFTP
  5. After upgrading, verify the new firmware version is installed
  6. Restrict physical access to the serial console port to prevent unauthorized access
Caveat Review PLANET release notes for any configuration or feature changes between versions before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gs 4210 24p2s Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8449 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-8449 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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