dbcve.org
Gecko OsOperating system · Silabs

CVE-2025-2837

HIGH · 8.8 CVSS v3.0 Published 2025-03-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
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
Silicon Labs Gecko OS HTTP Request Handling Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Silicon Labs Gecko OS. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of HTTP requests. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the device. Was ZDI-CAN-23245.

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

A stack-based buffer overflow vulnerability in Silicon Labs Gecko OS allows network-adjacent attackers to execute arbitrary code by sending specially crafted HTTP requests. The flaw exists in the HTTP request handling code, which fails to validate the length of user-supplied data before copying it into a fixed-size stack buffer, enabling code execution in the device context.

MitigationApply vendor-supplied firmware updates when available; in the interim, isolate affected devices on restricted network segments and limit HTTP access from untrusted networks.

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
Gecko OsOperating system
Affected:= 1.0.46

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

CVSS:3.0/AV:A/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. Confirm device runs Silicon Labs Gecko OS
    Identify the device firmware or OS by checking the boot logs, system information, or firmware banner for 'Gecko OS' or 'Silicon Labs' branding. Consult device documentation if available.
    Affected if The device does not run Gecko OS (not affected)
  2. Determine installed Gecko OS version
    Access the device CLI or web interface and run the command to display firmware version, such as 'get version' or 'system info'. Alternatively, inspect the firmware file metadata if you have access to the firmware binary.
    Affected if Installed version is exactly 1.0.46 (vulnerable); versions different from 1.0.46 are not affected by this specific CVE
  3. Verify HTTP server is enabled
    Check the device configuration for HTTP server settings via CLI command like 'get network.http' or via the web management interface. The vulnerability exists in HTTP request handling.
    Affected if HTTP server is enabled and the device runs Gecko OS 1.0.46 (vulnerable condition requires both)
  4. Assess network accessibility
    Determine if the device HTTP service is accessible from untrusted network segments. Check if the device is on the same network segment as untrusted users or if it has a directly exposed IP address on an untrusted interface.
    Affected if Device HTTP service is network-adjacent accessible to untrusted attackers (exploitation requires adjacent network access)

The device is affected if it runs Gecko OS version 1.0.46, has HTTP server enabled, and is accessible to network-adjacent attackers.

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

Apply vendor-supplied firmware updates when available; in the interim, isolate affected devices on restricted network segments and limit HTTP access from untrusted networks.

Fix this in Gecko Os Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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