| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Apple OS X Server up to 5.0 and classified as problematic. This affects an unknown part of the component Wiki Server. The manipulation leads to information disclosure. This vulnerability is listed as CVE-2016-1787. There is no available exploit. The affected component should be upgraded.
Details
A vulnerability was found in Apple OS X Server up to 5.0. It has been rated as problematic. This issue affects an unknown part of the component Wiki Server. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
Wiki Server in Apple OS X Server before 5.1 allows remote attackers to obtain sensitive information from Wiki pages via unspecified vectors.
The weakness was presented 03/19/2016 as HT206173 as confirmed advisory (Website). The advisory is shared at support.apple.com. The identification of this vulnerability is CVE-2016-1787. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue. The advisory points out:
An access issue existed in some Wiki pages. This issue was addressed through improved access restrictions.
Upgrading to version 5.1 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at SecurityFocus (BID 85054†) and Vulnerability Center (SBV-57503†). See VDB-81410, VDB-81411, VDB-81412 and VDB-94405 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.apple.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
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: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: OS X Server 5.1
Timeline
01/13/2016 🔍03/19/2016 🔍
03/19/2016 🔍
03/21/2016 🔍
03/22/2016 🔍
03/22/2016 🔍
03/23/2016 🔍
07/10/2022 🔍
Sources
Vendor: apple.comAdvisory: HT206173
Status: Confirmed
CVE: CVE-2016-1787 (🔍)
GCVE (CVE): GCVE-0-2016-1787
GCVE (VulDB): GCVE-100-81413
SecurityFocus: 85054
SecurityTracker: 1035342
Vulnerability Center: 57503 - Apple OS X Server before 5.1 Remote Information Disclosure due to a Flaw in Wiki Server - CVE-2016-1787, Medium
scip Labs: https://www.scip.ch/en/?labs.20150108
See also: 🔍
Entry
Created: 03/23/2016 12:01Updated: 07/10/2022 16:11
Changes: 03/23/2016 12:01 (45), 06/21/2016 09:14 (16), 07/10/2022 16:04 (4), 07/10/2022 16:11 (10)
Complete: 🔍
Cache ID: 216:37C: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.