dbcve.org
Gs 4210 24p2s FirmwareOperating system · Planet

CVE-2024-8458

HIGH · 8.8 CVSS v3.1 Published 2024-09-30
Fix available
A fix is available. Upgrade to 2.305b240719 / 3.305b240802 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 web application that is vulnerable to Cross-Site Request Forgery (CSRF). An unauthenticated remote attacker can trick a user into visiting a malicious website, allowing the attacker to impersonate the user and perform actions on their behalf, such as creating accounts.

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

CSRF vulnerability in the web application of PLANET Technology switches allows unauthenticated remote attackers to trick authenticated users into performing unintended state-changing actions such as creating new administrative accounts by embedding malicious requests in external websites.

MitigationImplement anti-CSRF tokens on all state-changing operations (forms, AJAX calls) and validate the Origin/Referer headers; alternatively, apply vendor-supplied firmware updates if available.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 switch model
    Access the device web interface or use SNMP/LDAP queries to determine the exact model number (Planet Gs 4210 24p2s or Planet Gs 4210 24pl4c)
    Affected if The device is a Planet Gs 4210 24p2s or 24pl4c model
  2. Check the installed firmware version
    Log into the web interface and navigate to the System Information or Firmware Upgrade page to view the current firmware version, or use the CLI command 'show version' if available
    Affected if Firmware version is below 3.305b240802 for the 24p2s model, or below 2.305b240719 for the 24pl4c model
  3. Verify the web application is accessible
    Attempt to access the device web management interface over HTTP/HTTPS
    Affected if The web interface is reachable and responds to authentication requests
  4. Determine if state-changing operations lack CSRF protections
    Inspect HTML forms or AJAX requests in the web interface for the presence of anti-CSRF tokens (such as hidden form fields named 'csrf_token', 'token', or similar) when performing actions like creating users or changing settings
    Affected if State-changing forms (user creation, configuration changes) do not contain anti-CSRF tokens or do not validate Origin/Referer headers

You are affected if you are running a Planet Gs 4210 24p2s or 24pl4c switch with firmware below the specified thresholds and the web interface lacks anti-CSRF protections on state-changing operations.

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

Implement anti-CSRF tokens on all state-changing operations (forms, AJAX calls) and validate the Origin/Referer headers; alternatively, apply vendor-supplied firmware updates if available.

Recommended fix Moderate confidence

Gs 4210 24p2s: firmware 3.305b240802 or later; Gs 4210 24pl4c: firmware 2.305b240719 or later

  1. 1. Identify the exact model number of the PLANET switch (Gs 4210 24p2s or Gs 4210 24pl4c)
  2. 2. Access the device web interface and navigate to the Firmware Upgrade or System Maintenance section
  3. 3. Check the current firmware version to confirm it is vulnerable (less than 3.305b240802 for 24p2s, or less than 2.305b240719 for 24pl4c)
  4. 4. Download the fixed firmware version from the official PLANET Technology website or support portal
  5. 5. Upload the firmware file through the web interface or appropriate update mechanism
  6. 6. Wait for the firmware upload and installation to complete (do not power off the device)
  7. 7. After reboot, verify the new firmware version is installed and the CSRF vulnerability is resolved
  8. 8. Consider implementing anti-CSRF tokens in custom applications if applicable
Caveat Standard firmware upgrade risks apply - ensure stable power during update and backup configuration if possible

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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