MiniUPnP MiniUPnPd up to 2.1 upnpsoap.c GetOutboundPinholeTimeout null pointer dereference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in MiniUPnP MiniUPnPd up to 2.1. The affected element is the function GetOutboundPinholeTimeout of the file upnpsoap.c. This manipulation causes null pointer dereference.
This vulnerability is tracked as CVE-2019-12109. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in MiniUPnP MiniUPnPd up to 2.1. It has been declared as problematic. Affected by this vulnerability is the function GetOutboundPinholeTimeout of the file upnpsoap.c. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect availability. The summary by CVE is:
A Denial Of Service vulnerability in MiniUPnP MiniUPnPd through 2.1 exists due to a NULL pointer dereference in GetOutboundPinholeTimeout in upnpsoap.c for rem_port.
The bug was discovered 02/06/2019. The weakness was disclosed 05/15/2019 (Website). The advisory is shared at lists.debian.org. This vulnerability is known as CVE-2019-12109 since 05/15/2019. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 98 days. During that time the estimated underground price was around $0-$5k. The commercial vulnerability scanner Qualys is able to test this issue with plugin 176953 (Debian Security Update for miniupnpd (DLA 1811-1)).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-111295, VDB-135095, VDB-135096 and VDB-135098 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
02/06/2019 🔍05/15/2019 🔍
05/15/2019 🔍
05/16/2019 🔍
09/21/2023 🔍
Sources
Advisory: 13585f15c7f7dc28bbbba1661efb280d530d114cStatus: Confirmed
CVE: CVE-2019-12109 (🔍)
GCVE (CVE): GCVE-0-2019-12109
GCVE (VulDB): GCVE-100-135097
See also: 🔍
Entry
Created: 05/16/2019 08:28Updated: 09/21/2023 08:07
Changes: 05/16/2019 08:28 (58), 06/12/2020 17:49 (2), 09/21/2023 08:01 (4), 09/21/2023 08:07 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.