pupnp: Port truncation via atoi() cast in parse_uri() allows SSRF port confusion
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| pupnp | pupnp | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Pupnp | Pupnp |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.346% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pupnp
Pupnp pupnp |
|
| Vendors & Products |
Pupnp
Pupnp pupnp |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | pupnp is an SDK for development of UPnP device and control point applications. Prior to version 1.18.5, pupnp is vulnerable to SRRF port confusion due to port truncation via atoi() cast in parse_uri(). This issue has been patched in version 1.18.5. | |
| Title | pupnp: Port truncation via atoi() cast in parse_uri() allows SSRF port confusion | |
| Weaknesses | CWE-195 CWE-918 |
|
| References |
| |
| Metrics |
cvssV4_0
|