OpenDNS OpenResolve resolverapi/endpoints.py neutralization for logs
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in OpenDNS OpenResolve. This affects an unknown part of the file resolverapi/endpoints.py. Performing a manipulation results in neutralization for logs. This vulnerability is reported as CVE-2015-10011. No exploit exists. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability classified as problematic has been found in OpenDNS OpenResolve (affected version unknown). This affects an unknown functionality of the file resolverapi/endpoints.py. The manipulation with an unknown input leads to a neutralization for logs vulnerability. CWE is classifying the issue as CWE-117. The product does not neutralize or incorrectly neutralizes output that is written to logs. This is going to have an impact on integrity, and availability.
The weakness was disclosed 01/02/2023 as 9eba6ba5abd89d0e36a008921eb307fcef8c5311. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2015-10011. Technical details are known, but no exploit is available.
Applying the patch 9eba6ba5abd89d0e36a008921eb307fcef8c5311 is able to eliminate this problem. The bugfix is ready for download at github.com. The advisory contains the following remark:
Log Injection Attack Vulnerability
By logging the unsanitized user input, a log injection attack canoccur. This commit removes user-provided values from the logs.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 4.6
CNA Vector (VulDB): 🔍
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: Neutralization for logsCWE: CWE-117 / CWE-116 / CWE-74
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 9eba6ba5abd89d0e36a008921eb307fcef8c5311
Timeline
01/02/2023 🔍01/02/2023 🔍
01/02/2023 🔍
01/27/2023 🔍
Sources
Product: github.comAdvisory: 9eba6ba5abd89d0e36a008921eb307fcef8c5311
Status: Confirmed
CVE: CVE-2015-10011 (🔍)
GCVE (CVE): GCVE-0-2015-10011
GCVE (VulDB): GCVE-100-217197
Entry
Created: 01/02/2023 22:05Updated: 01/27/2023 02:43
Changes: 01/02/2023 22:05 (40), 01/27/2023 02:35 (2), 01/27/2023 02:43 (28)
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.