Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 20 Oct 2026 19:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pupnp Project
Pupnp Project pupnp |
|
| CPEs | cpe:2.3:a:pupnp_project:pupnp:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Pupnp Project
Pupnp Project pupnp |
Fri, 16 Oct 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 16 Oct 2026 15:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | pupnp is an SDK for development of UPnP device and control point applications. Prior to 2.0.2, raw_to_int in upnp/src/genlib/net/http/httpparser.c parses Content-Length with strtol and casts the resulting long to a 32-bit int before the caller stores it as unsigned int. On LP64 systems, values greater than INT_MAX can truncate or wrap, so the HTTP parser can accept a body length different from the declared value. A remote adjacent-network peer can use the resulting parser disagreement to leave bytes to be interpreted as another request in persistent or proxied contexts, or can make a worker wait for an extremely large body and cause denial of service. This issue is fixed in 2.0.2. | |
| Title | pupnp: Integer truncation in HTTP Content-Length parsing enables request smuggling | |
| Weaknesses | CWE-190 CWE-444 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-16T19:08:25.462Z
Reserved: 2026-06-24T14:53:40.111Z
Link: CVE-2026-57488
Updated: 2026-10-16T19:08:18.492Z
Status : Analyzed
Published: 2026-10-16T16:18:44.823
Modified: 2026-10-20T19:37:12.947
Link: CVE-2026-57488
No data.
OpenCVE Enrichment
Updated: 2026-10-16T18:00:16Z