dbcve.org
Gs 4210 24p2s FirmwareOperating system · Planet

CVE-2024-8456

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 lack proper access control in firmware upload and download functionality, allowing unauthenticated remote attackers to download and upload firmware and system configurations, ultimately gaining full control of the devices.

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 confidence

PLANET Technology switches have a critical authentication bypass in their firmware management interface. The lack of access controls on firmware upload/download functions allows any remote unauthenticated attacker to retrieve or modify device firmware and configurations, achieving complete device compromise.

MitigationImmediately restrict network access to management interfaces using firewalls or ACLs, apply vendor firmware updates when available, and disable remote firmware management if not required.

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 the exact switch model
    Log into the device web interface or CLI and locate the model name displayed in the system information or device status page. Alternatively, check the physical device label or network inventory documentation.
    Affected if The model is Planet Gs 4210 24p2s or Planet Gs 4210 24pl4c.
  2. Determine the installed firmware version
    In the web interface, navigate to System > Firmware or System > Device Information to view the current firmware version. In CLI, use 'show version' or 'show system-info'. Compare the version number to the affected ranges: < 3.305b240802 for 24p2s, < 2.305b240719 for 24pl4c.
    Affected if The installed firmware version is lower than 3.305b240802 (for 24p2s) or lower than 2.305b240719 (for 24pl4c).
  3. Verify if the web-based firmware management interface is remotely accessible
    From an external network location, attempt to access the device login page via HTTP/HTTPS on the management IP address (typically ports 80 or 443). If the interface loads without VPN or authentication, it is remotely exposed.
    Affected if The firmware management web interface is reachable from untrusted networks without authentication.
  4. Check if firmware upload/download functions are accessible without authentication
    Attempt to access common firmware management URLs directly without logging in, such as /cgi-bin/firmware.cgi, /cgi-bin/upload.cgi, or /backup.cgi. Use tools like curl to send requests to these endpoints and observe if they return firmware files or configuration dumps without requiring credentials.
    Affected if Firmware or configuration files can be retrieved or uploaded without providing valid authentication credentials.

A user is affected if they operate a Gs 4210 24p2s or Gs 4210 24pl4c switch with firmware below the specified versions AND the firmware management interface is accessible without authentication.

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

Immediately restrict network access to management interfaces using firewalls or ACLs, apply vendor firmware updates when available, and disable remote firmware management if not required.

Recommended fix High confidence

Firmware version 3.305b240802 or later for Gs 4210 24p2s; Firmware version 2.305b240719 or later for Gs 4210 24pl4c

  1. Identify the exact model of PLANET Technology switch (Gs 4210 24p2s or Gs 4210 24pl4c) in your environment
  2. Access the device's web management interface or console
  3. Navigate to the firmware upgrade section (typically under System > Firmware Upgrade or Maintenance > Upgrade)
  4. Download the firmware update from PLANET Technology's official support website - ensure the version is >= 3.305b240802 for Gs 4210 24p2s or >= 2.305b240719 for Gs 4210 24pl4c
  5. Upload the firmware file to the device and allow the upgrade process to complete
  6. After reboot, verify the firmware version has been updated successfully
  7. Ensure the device is not directly exposed to the internet and implement network segmentation as a defense-in-depth measure
Caveat Review release notes for any configuration changes required after upgrade; backup current configuration 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
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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