dbcve.org
Heap-based Buffer OverflowWeakness · CWE-122

CVE-2025-45029

MEDIUM · 6.5 CVSS v3.1 Published 2025-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
WINSTAR WN572HP3 v230525 was discovered to contain a heap overflow via the CONTENT_LENGTH variable at /cgi-bin/upload.cgi.

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

Heap overflow vulnerability in the WINSTAR WN572HP3 wireless access point's CGI upload handler (/cgi-bin/upload.cgi). The CONTENT_LENGTH parameter is not properly validated before use in heap memory operations, allowing an attacker to overflow the heap buffer and potentially achieve remote code execution.

MitigationContact WINSTAR for firmware patch; restrict network access to the device's management interface, disable the upload functionality if not needed, and monitor for unauthorized access attempts.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access the device's web interface or check the device label/marketing materials to confirm the model is WINSTAR WN572HP3
    Affected if The device is a WINSTAR WN572HP3 unit
  2. Verify CGI upload handler exists
    Attempt to access or probe the URL /cgi-bin/upload.cgi on the device's web server
    Affected if The endpoint responds or is accessible (indicates the vulnerable CGI handler is present)
  3. Confirm upload functionality is enabled
    Check the device's administrative web interface for an upload feature (firmware upgrade, configuration import, etc.)
    Affected if Upload functionality is present and enabled in the device configuration
  4. Check network exposure
    Determine if the device's management interface (HTTP/HTTPS on port 80/443) is accessible from untrusted networks
    Affected if The device management interface is exposed to the internet or untrusted LAN segments
  5. Assess authentication status
    Verify whether the device requires authentication for accessing /cgi-bin/upload.cgi or if it can be reached without valid credentials
    Affected if The upload endpoint is accessible without authentication or uses weak/default credentials

You are affected if you have a WINSTAR WN572HP3 device with the vulnerable upload.cgi handler accessible on your network, particularly if the management interface is exposed or the upload feature is enabled.

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

Contact WINSTAR for firmware patch; restrict network access to the device's management interface, disable the upload functionality if not needed, and monitor for unauthorized access attempts.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,730
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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