| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in LPRng up to 3.7.4 on Red Hat. It has been rated as problematic. This issue affects some unknown processing. The manipulation leads to privileges management. This vulnerability is traded as CVE-2001-0787. Furthermore, there is an exploit available.
Details
A vulnerability was found in LPRng up to 3.7.4 on Red Hat. It has been rated as problematic. This issue affects an unknown function. The manipulation with an unknown input leads to a privileges management vulnerability. Using CWE to declare the problem leads to CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
LPRng in Red Hat Linux 7.0 and 7.1 does not properly drop memberships in supplemental groups when lowering privileges, which could allow a local user to elevate privileges.
The bug was discovered 06/03/2001. The weakness was shared 10/18/2001 by zen-parse with Redhat (Website). The advisory is shared at redhat.com. The identification of this vulnerability is CVE-2001-0787. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
A public exploit has been developed in ANSI C. The exploit is available at securityfocus.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 137 days. During that time the estimated underground price was around $0-$5k.
The vulnerability is also documented in the databases at X-Force (6703), Exploit-DB (20923), SecurityFocus (BID 2865†), OSVDB (1866†) and Vulnerability Center (SBV-20396†). The entry VDB-16817 is related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.9
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Privileges managementCWE: CWE-269 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Programming Language: 🔍
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
06/03/2001 🔍06/07/2001 🔍
06/07/2001 🔍
10/18/2001 🔍
10/18/2001 🔍
01/08/2009 🔍
07/09/2014 🔍
01/13/2025 🔍
Sources
Advisory: redhat.comResearcher: zen-parse
Organization: Redhat
Status: Confirmed
CVE: CVE-2001-0787 (🔍)
GCVE (CVE): GCVE-0-2001-0787
GCVE (VulDB): GCVE-100-17549
X-Force: 6703 - LPRng fails to drop supplementary groups
SecurityFocus: 2865 - LPRng Failure To Drop Supplementary Groups Vulnerability
OSVDB: 1866 - LPRng - Failure To Drop Supplementary Groups Issue
Vulnerability Center: 20396 - Red Hat Linux 7.0 and 7.1 LPRng Local Privilege Escalation Vulnerability, Medium
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 07/09/2014 17:44Updated: 01/13/2025 03:20
Changes: 07/09/2014 17:44 (65), 08/23/2019 10:05 (3), 01/13/2025 03:20 (17)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.