Menu

Star on GitHub · 3.3k

CVE-2018-25049

3.0 · LOW

A vulnerability was found in email-existence.

Published Dec 27, 2022CWE-1333EPSS 0.76%

Overview

CVE-2018-25049 is a low-severity vulnerability. It was published on December 27, 2022 and has a CVSS 3.1 base score of 3.0 (LOW).

This vulnerability has a CVSS 3.1 base score of 3.0, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

A vulnerability was found in email-existence. It has been rated as problematic. Affected by this issue is some unknown functionality of the file index.js. The manipulation leads to inefficient regular expression complexity. The name of the patch is 0029ba71b6ad0d8ec0baa2ecc6256d038bdd9b56. It is recommended to apply a patch to fix this issue. VDB-216854 is the identifier assigned to this vulnerability.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2018-25049?

CVE-2018-25049 is a low-severity vulnerability. It was published on December 27, 2022 and has a CVSS 3.1 base score of 3.0 (LOW).

How severe is CVE-2018-25049?

This vulnerability has a CVSS 3.1 base score of 3.0, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2018-25049?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2018-25049?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2018-25049 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2018

View all
LiveWatch live →