CVE-2024-2740
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 · uneditedInformation exposure vulnerability in Planet IGS-4215-16T2S, affecting firmware version 1.305b210528. This vulnerability could allow a remote attacker to access some administrative resources due to lack of proper management of the Switch web interface.
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 confidenceAn information exposure vulnerability in the Planet IGS-4215-16T2S switch's web interface (firmware 1.305b210528) allows remote attackers to access administrative resources due to improper management of the web interface. The CVSS 7.7 indicates the vulnerability is exploitable and leads to exposure of sensitive administrative information or functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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 the device modelAccess the switch via console or network and check the hardware model. The affected model is Planet IGS-4215-16T2S. Use 'show system' or check the device label/web interface for model identification.Affected if The device is an IGS-4215-16T2S switch from Planet Technology
-
Check the firmware versionAccess the switch CLI via console or SSH and run 'show version' or 'show firmware'. Alternatively, log into the web interface and navigate to System > Firmware or System Information to view the running firmware version.Affected if The firmware version is 1.305b210528 or earlier (the specific version mentioned in the advisory)
-
Verify web interface statusLog into the switch CLI and run 'show ip http' or 'show web' to check if the HTTP/HTTPS web interface is enabled. Also check if remote web management is permitted.Affected if The web interface is enabled and accessible from remote networks (not limited to localhost/console)
-
Check web management access controlIn the web interface, go to System > IP Access or Management Access settings. Verify whether remote web management is allowed and from which IP addresses. Check if there's an ACL restricting web access to trusted IPs only.Affected if Remote web management is enabled without IP restrictions or trusted network limitations
You are affected if you have a Planet IGS-4215-16T2S switch running firmware version 1.305b210528 with the web interface exposed to untrusted networks.
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.
From vendor dataContact Planet Technology for firmware updates addressing this vulnerability. If no patch is available, restrict web interface access to trusted networks or disable remote web management until a fix is released.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2740 — 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-2740 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