CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
7.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in phpwhois. It has been classified as critical. This affects an unknown part of the component Whois Record Handler. The manipulation leads to code injection. This vulnerability is uniquely identified as CVE-2015-5243. It is possible to initiate the attack remotely. There is no exploit available. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Details
A vulnerability was found in phpwhois (unknown version) and classified as critical. Affected by this issue is an unknown code block of the component Whois Record Handler. The manipulation with an unknown input leads to a code injection vulnerability. Using CWE to declare the problem leads to CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. Impacted is confidentiality, integrity, and availability. CVE summarizes:
phpWhois allows remote attackers to execute arbitrary code via a crafted whois record.
The bug was discovered 08/01/2018. The weakness was shared 08/20/2018 (GitHub Repository). The advisory is shared for download at github.com. This vulnerability is handled as CVE-2015-5243 since 07/01/2015. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1059.
The vulnerability was handled as a non-public zero-day exploit for at least 19 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.8
VulDB Base Score: 6.3
VulDB Temp Score: 5.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Code injectionCWE: CWE-94 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
07/01/2015 🔍08/01/2018 🔍
08/20/2018 🔍
08/20/2018 🔍
08/21/2018 🔍
05/02/2023 🔍
Sources
Advisory: 91c937e03c876ba1290b6de2a3ad953d2105fdd0Status: Not defined
Confirmation: 🔍
CVE: CVE-2015-5243 (🔍)
GCVE (CVE): GCVE-0-2015-5243
GCVE (VulDB): GCVE-100-123044
Entry
Created: 08/21/2018 06:43 AMUpdated: 05/02/2023 02:59 PM
Changes: 08/21/2018 06:43 AM (54), 03/16/2020 08:42 PM (2), 05/02/2023 02:59 PM (5)
Complete: 🔍
Cache ID: 18:7B7:40
No comments yet. Languages: en.
Please log in to comment.