OpenBSD 6.6 libc gen/auth_subr.c Username improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in OpenBSD 6.6. It has been classified as critical. This impacts an unknown function of the file gen/auth_subr.c of the component libc. This manipulation with the input schallenge as part of Username causes improper authentication.
This vulnerability appears as CVE-2019-19521. The attack may be initiated remotely. There is no available exploit. This vulnerability is considered historic because of its background and reception.
Details
A vulnerability classified as critical was found in OpenBSD 6.6 (Operating System). Affected by this vulnerability is an unknown code block of the file gen/auth_subr.c of the component libc. The manipulation with the input value schallenge leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
libc in OpenBSD 6.6 allows authentication bypass via the -schallenge username, as demonstrated by smtpd, ldapd, or radiusd. This is related to gen/auth_subr.c and gen/authenticate.c in libc (and login/login.c and xenocara/app/xenodm/greeter/verify.c).
The weakness was presented 12/05/2019 (oss-sec). It is possible to read the advisory at openwall.com. This vulnerability is known as CVE-2019-19521. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 03/07/2024). Due to its background and reception, this vulnerability has a historic impact.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-146681 and VDB-146682 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Improper authenticationCWE: CWE-287
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/03/2019 🔍12/05/2019 🔍
12/05/2019 🔍
03/07/2024 🔍
Sources
Advisory: 155572Status: Not defined
CVE: CVE-2019-19521 (🔍)
GCVE (CVE): GCVE-0-2019-19521
GCVE (VulDB): GCVE-100-146683
See also: 🔍
Entry
Created: 12/05/2019 08:26Updated: 03/07/2024 13:27
Changes: 12/05/2019 08:26 (42), 12/05/2019 08:31 (17), 03/07/2024 13:27 (4)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.