| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in FreeBSD 3.3. It has been rated as problematic. This issue affects some unknown processing of the file .wmmonrc of the component WMMon. This manipulation causes privileges management. This vulnerability is registered as CVE-2000-0018. Furthermore, an exploit is available. Upgrading the affected component is advised.
Details
A vulnerability classified as critical was found in FreeBSD 3.3 (Operating System). Affected by this vulnerability is an unknown function of the file .wmmonrc of the component WMMon. The manipulation with an unknown input leads to a privileges management vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
wmmon in FreeBSD allows local users to gain privileges via the .wmmonrc configuration file.
The weakness was published 12/22/1999 by Steve Reid (FIRST) (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2000-0018. The exploitation appears to be easy. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1068 for this issue.
After even before and not, there has been an exploit disclosed. It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $5k-$25k.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (4382), Exploit-DB (19685), SecurityFocus (BID 885†) and OSVDB (1169†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
Website
- Product: https://www.freebsd.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.4VulDB Meta Temp Score: 7.6
VulDB Base Score: 8.4
VulDB Temp Score: 7.6
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
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
12/21/1999 🔍12/22/1999 🔍
12/22/1999 🔍
12/22/1999 🔍
02/21/2003 🔍
06/22/2014 🔍
09/13/2024 🔍
Sources
Product: freebsd.orgAdvisory: securityfocus.com⛔
Researcher: Steve Reid (FIRST)
Status: Not defined
CVE: CVE-2000-0018 (🔍)
GCVE (CVE): GCVE-0-2000-0018
GCVE (VulDB): GCVE-100-15085
X-Force: 4382
SecurityFocus: 885 - FreeBSD WMMon Vulnerability
OSVDB: 1169 - FreeBSD WMMon Privilege Escalation
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 06/22/2014 16:19Updated: 09/13/2024 06:18
Changes: 06/22/2014 16:19 (59), 04/05/2019 09:39 (1), 09/13/2024 06:18 (25)
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.