dbcve.org
MiniupnpdApplication · Miniupnp Project

CVE-2013-0229

HIGH · 7.8 CVSS v2.0 Published 2013-01-31
Fix available
A fix is available. Upgrade to after 1.3 or later.
See remediation →
87/100
Remediation priority · High
High EPSS 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
The ProcessSSDPRequest function in minissdp.c in the SSDP handler in MiniUPnP MiniUPnPd before 1.4 allows remote attackers to cause a denial of service (service crash) via a crafted request that triggers a buffer over-read.

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

Buffer over-read vulnerability in the ProcessSSDPRequest function in minissdp.c in the SSDP handler of MiniUPnP MiniUPnPd before version 1.4. Remote attackers can send crafted SSDP requests to trigger the over-read, causing the service to crash.

MitigationUpgrade MiniUPnPd to version 1.4 or later to patch the buffer over-read in the SSDP handler.

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
MiniupnpdApplication
Affected:<= 1.3= 1.0= 1.1= 1.2

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
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:N/C:N/I:N/A:C

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 MiniUPnPd installed version
    Run 'miniupnpd -v' or check via package manager (dpkg -l miniupnpd, rpm -qa miniupnpd) or examine the binary with 'miniupnpd --version'
    Affected if Version is 1.3 or lower, or specifically 1.0, 1.1, or 1.2 (any version before 1.4)
  2. Confirm SSDP handler is exposed
    Check if miniupnpd process is running and listening on UDP port 1900 (SSDP multicast). Use 'netstat -anup | grep 1900' or 'ss -anup | grep 1900'
    Affected if SSDP service is active and version is in the affected range
  3. Locate vulnerable minissdp.c source
    If source is available, check the minissdp.c file for the ProcessSSDPRequest function. Compare file modification date or version markers against the 1.4 patch release
    Affected if Source file predates the 1.4 fix and contains the ProcessSSDPRequest function without the boundary check fix
  4. Review SSDP request handling configuration
    Examine MiniUPnPd configuration files (typically miniupnpd.conf or similar) for SSDP enablement settings. Check logs for any crash events related to SSDP requests
    Affected if SSDP is enabled and logs show recent crashes, or config confirms SSDP is active on vulnerable version

User is affected if MiniUPnPd version is 1.3 or lower and the SSDP handler is actively listening on port 1900, exposing the vulnerable ProcessSSDPRequest function to network requests.

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
Upgrade available Upgrade to a release after 1.3
Interim mitigation

Upgrade MiniUPnPd to version 1.4 or later to patch the buffer over-read in the SSDP handler.

Fix this in Miniupnpd Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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