| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Host. Affected is an unknown function of the component NIS Server. The manipulation leads to privileges management. This vulnerability is uniquely identified as CVE-1999-0620. No exploit exists. You should change the configuration settings. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability was found in Host (affected version not known) and classified as critical. This issue affects some unknown functionality of the component NIS Server. 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:
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: None. Reason: this candidate is solely about a configuration that does not directly introduce security vulnerabilities, so it is more appropriate to cover under the Common Configuration Enumeration (CCE). Notes: the former description is: "A component service related to NIS is running."
The weakness was disclosed 01/01/1999. The identification of this vulnerability is CVE-1999-0620. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
It is possible to mitigate the problem by applying the configuration setting .
The vulnerability is also documented in the vulnerability database at Vulnerability Center (SBV-424†). The entries VDB-14391, VDB-14390, VDB-14389 and VDB-14388 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.3
VulDB Temp Score: 7.1
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: 🔍
Exploiting
Class: Privileges managementCWE: CWE-269 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: ConfigStatus: 🔍
0-Day Time: 🔍
Timeline
01/01/1999 🔍01/01/1999 🔍
06/19/2014 🔍
06/08/2024 🔍
Sources
Status: Not definedCVE: CVE-1999-0620 (🔍)
GCVE (CVE): GCVE-0-1999-0620
GCVE (VulDB): GCVE-100-14387
Vulnerability Center: 424
See also: 🔍
Entry
Created: 06/20/2014 01:24 AMUpdated: 06/08/2024 08:22 PM
Changes: 06/20/2014 01:24 AM (37), 06/08/2024 08:22 PM (16)
Complete: 🔍
Cache ID: 244:413:40
No comments yet. Languages: en.
Please log in to comment.