Email::Address up to 1.909 on Perl parse algorithmic complexity
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.3 | $0-$5k | 0.00 |
A vulnerability, which was classified as problematic, was found in Email::Address up to 1.909 on Perl. Affected is the function parse
. The manipulation with an unknown input leads to a algorithmic complexity vulnerability. CWE is classifying the issue as CWE-407. An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached. This is going to have an impact on availability. CVE summarizes:
The parse() method in the Email::Address module through 1.909 for Perl is vulnerable to Algorithmic complexity on specially prepared input, leading to Denial of Service. Prepared special input that caused this problem contained 30 form-field characters ("\f").
The bug was discovered 06/19/2018. The weakness was published 06/20/2018 (oss-sec). The advisory is available at openwall.com. This vulnerability is traded as CVE-2018-12558 since 06/19/2018. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1499 by the MITRE ATT&CK project.
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 $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 121235 (Fedora 29 : perl-Email-Address (2019-026d5ab23d)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Fedora Local Security Checks and running in the context l.
Upgrading eliminates this vulnerability. A possible mitigation has been published 8 months after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (121235). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: Algorithmic complexityCWE: CWE-407 / CWE-404
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 |
Nessus ID: 121235
Nessus Name: Fedora 29 : perl-Email-Address (2019-026d5ab23d)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
06/19/2018 🔍06/19/2018 🔍
06/20/2018 🔍
06/20/2018 🔍
06/20/2018 🔍
01/18/2019 🔍
01/18/2019 🔍
03/28/2023 🔍
Sources
Advisory: FEDORA-2019-026d5ab23dStatus: Not defined
CVE: CVE-2018-12558 (🔍)
GCVE (CVE): GCVE-0-2018-12558
GCVE (VulDB): GCVE-100-119730
Entry
Created: 06/20/2018 10:51 PMUpdated: 03/28/2023 10:04 AM
Changes: 06/20/2018 10:51 PM (61), 02/20/2020 05:08 PM (10), 03/28/2023 10:04 AM (4)
Complete: 🔍
Cache ID: 18:34C:40
No comments yet. Languages: en.
Please log in to comment.