dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-3697

MEDIUM · 6.3 CVSS v3.1 Published 2026-03-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
A vulnerability was determined in Planet ICG-2510 1.0_20250811. The impacted element is the function sub_40C8E4 of the file /usr/sbin/httpd of the component Language Package Configuration Handler. Executing a manipulation of the argument Language can lead to stack-based buffer overflow. The attack can be launched remotely. The vendor was contacted early about this disclosure but did not respond in any way.

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

Stack-based buffer overflow in Planet ICG-2510 firmware's httpd daemon (function sub_40C8E4 in Language Package Configuration Handler). The vulnerability is triggered by manipulating the Language parameter in HTTP requests, allowing potential remote code execution.

MitigationNetwork-level filtering (restrict access to HTTP/HTTPS ports from untrusted sources) and consider web application firewall rules until vendor-supplied firmware update is available.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 device model
    Access the device's web interface or CLI and retrieve the model information. For web interface, check the login page or system status page. For CLI, use 'show system info' or similar command.
    Affected if Device is NOT a Planet ICG-2510 (different models are not affected by this specific CVE)
  2. Retrieve the firmware version
    In the web interface, navigate to System > Firmware or System > Status to view the installed firmware version. In CLI, use 'show version' or 'firmware version' command.
    Affected if Firmware version is within the affected range (cannot determine exact range from provided data; compare against vendor's advisory)
  3. Verify the httpd service is running
    Access the device via SSH or console and check for httpd process: 'ps | grep httpd' or check service status. The web interface must be active for the vulnerability to be exploitable.
    Affected if httpd service is not running (the vulnerability cannot be triggered if the service is disabled)
  4. Confirm web interface accessibility
    Attempt to access the device's HTTP/HTTPS ports from a test system: 'curl -I http://<device-ip>/' or 'curl -k https://<device-ip>/'. The Language parameter vulnerability requires the web interface to be reachable.
    Affected if Web interface is not accessible on HTTP/HTTPS ports (vulnerability requires network access to the web service)
  5. Check for Language Package Configuration Handler exposure
    Identify if the Language configuration feature is accessible. Attempt a basic GET request to common management paths or check if the Language parameter UI exists in System > Language or similar settings page.
    Affected if The Language Package Configuration Handler is not present or not accessible in the installed firmware version

The environment is affected if this is a Planet ICG-2510 device with a vulnerable firmware version where the httpd service is running and the web interface (including the Language parameter handler) is accessible over the network.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Network-level filtering (restrict access to HTTP/HTTPS ports from untrusted sources) and consider web application firewall rules until vendor-supplied firmware update is available.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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