dbcve.org
Gs 4210 24p2s FirmwareOperating system · Planet

CVE-2024-8450

CRITICAL · 9.8 CVSS v3.1 Published 2024-09-30
Fix available
A fix is available. Upgrade to 2.305b240719 / 3.305b240802 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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 community string in the SNMPv1 service, allowing unauthorized remote attackers to use this community string to access the SNMPv1 service with read-write privileges.

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 community string in the SNMPv1 service. SNMPv1 uses community strings as a primitive authentication mechanism, and when these are hard-coded and publicly known, attackers can use them to gain unauthorized read-write access to the device via SNMP queries.

MitigationReplace the default community strings with unique, complex values on all affected devices. Where possible, disable SNMPv1 and upgrade to SNMPv3 which supports authentication and encryption, or at minimum restrict SNMP access to authorized IP addresses via ACLs.

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
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 checks

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

  1. Identify switch model
    Access the device CLI or web interface and run 'show system' or check the device label/menu to confirm the exact model is Planet Gs 4210 24p2s or Planet Gs 4210 24pl4c
    Affected if Model is Gs 4210 24p2s or Gs 4210 24pl4c
  2. Check firmware version
    Run 'show version' in CLI or check the firmware info in the web management interface to determine the installed firmware version
    Affected if Firmware version is below 3.305b240802 for Gs 4210 24p2s, or below 2.305b240719 for Gs 4210 24pl4c
  3. Verify SNMPv1 status
    Run 'show snmp' or check SNMP configuration in the web interface to see if SNMP is enabled and which versions (v1/v2c/v3) are active
    Affected if SNMPv1 is enabled on the device
  4. Inspect community string configuration
    Run 'show running-config | include snmp' or access SNMP settings in the web interface to view the configured community strings
    Affected if The community strings cannot be modified, or a known default community string is still in use, indicating a hard-coded value

The device is affected if it is a Gs 4210 24p2s or Gs 4210 24pl4c model running firmware below the specified version threshold AND has SNMPv1 enabled.

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

Replace the default community strings with unique, complex values on all affected devices. Where possible, disable SNMPv1 and upgrade to SNMPv3 which supports authentication and encryption, or at minimum restrict SNMP access to authorized IP addresses via ACLs.

Recommended fix High confidence

Gs 4210 24p2s: firmware >= 3.305b240802 | Gs 4210 24pl4c: firmware >= 2.305b240719

  1. Identify the exact model of the PLANET switch (Gs 4210 24p2s or Gs 4210 24pl4c) in your environment
  2. Navigate to the vendor's official support/download page for the specific model
  3. Download the firmware version 3.305b240802 or later for Gs 4210 24p2s, or version 2.305b240719 or later for Gs 4210 24pl4c
  4. Review the vendor's firmware upgrade instructions document
  5. Connect to the switch management interface via console or web UI
  6. Backup the current switch configuration before proceeding with firmware upgrade
  7. Upload the new firmware file through the management interface
  8. Initiate the firmware upgrade and allow the process to complete without power interruption
Caveat Standard firmware upgrade risks apply - ensure configuration backup and planned maintenance window

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
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
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,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8450 — 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-8450 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