libpcap up to 1.9.0 rpcapd/daemon.c Username data authenticity
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in libpcap up to 1.9.0 and classified as problematic. The affected element is an unknown function of the file rpcapd/daemon.c. Performing a manipulation results in data authenticity (Username). This vulnerability is cataloged as CVE-2019-15162. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability classified as problematic has been found in libpcap up to 1.9.0. This affects an unknown part of the file rpcapd/daemon.c. The manipulation with an unknown input leads to a data authenticity vulnerability (Username). CWE is classifying the issue as CWE-345. The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. This is going to have an impact on confidentiality. The summary by CVE is:
rpcapd/daemon.c in libpcap before 1.9.1 on non-Windows platforms provides details about why authentication failed, which might make it easier for attackers to enumerate valid usernames.
The weakness was shared 10/03/2019 (GitHub Repository). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2019-15162 since 08/19/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
Upgrading to version 1.9.1 eliminates this vulnerability.
The entries VDB-142928, VDB-142930, VDB-142931 and VDB-142932 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.3
VulDB Temp Score: 4.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
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
Name: UsernameClass: Data authenticity / Username
CWE: CWE-345
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: libpcap 1.9.1
Patch: github.com
Timeline
08/19/2019 🔍10/03/2019 🔍
10/04/2019 🔍
01/03/2024 🔍
Sources
Advisory: 484d60cbf7ca4ec758c3cbb8a82d68b244a78d58Status: Not defined
Confirmation: 🔍
CVE: CVE-2019-15162 (🔍)
GCVE (CVE): GCVE-0-2019-15162
GCVE (VulDB): GCVE-100-142929
See also: 🔍
Entry
Created: 10/04/2019 09:13Updated: 01/03/2024 10:58
Changes: 10/04/2019 09:13 (57), 09/21/2020 10:22 (1), 01/03/2024 10:52 (5), 01/03/2024 10:58 (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.