LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25049: email-existence index.js redos

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.

LowCVSS 3Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2018-25049 is a low-severity denial-of-service issue in email-existence. A regular expression in index.js can perform inefficiently, potentially slowing or disrupting the affected process. The sources name a patch commit but do not provide affected version ranges or evidence of active exploitation.

Executive priority

Handle through normal dependency maintenance unless the library is used in high-volume registration, contact, or onboarding paths. There is no cited active exploitation and the assessed impact is limited availability loss, but missing version data means inventory confirmation matters.

Technical view

The issue is classified as CWE-1333: inefficient regular expression complexity, commonly associated with ReDoS risk. CVSS 3.1 is 3.0 with adjacent attack vector, low attack complexity, low privileges, user interaction required, and low availability impact only. The referenced fix is commit 0029ba71b6ad0d8ec0baa2ecc6256d038bdd9b56.

Likely exposure

Exposure is most likely in applications that include email-existence and pass user-controlled email values into its index.js validation logic. The source bundle does not identify affected versions, so teams must confirm dependency presence and patch status directly in their codebase and dependency metadata.

Exploitation context

No CISA KEV entry or cited source indicates active exploitation. Based on the CVSS vector, exploitation requires adjacent access, low privileges, and user interaction, with impact limited to availability. Evidence is insufficient to claim remote internet-wide exploitation or data compromise.

Researcher notes

The public record is sparse: affected versions and exact vulnerable functionality are not specified beyond index.js. Treat the GitHub pull request and patch commit as the primary remediation evidence. Avoid expanding scope beyond email-existence unless local dependency analysis proves bundled or vendored copies.

Mitigation direction

  • Apply the referenced project patch commit where the dependency is used.
  • Check project guidance for any release containing the patch.
  • Replace or remove email-existence if no maintained patched release is available.
  • Add request timeouts or input processing limits around email validation paths.

Validation and detection

  • Search application manifests and lockfiles for email-existence.
  • Confirm deployed source includes commit 0029ba71b6ad0d8ec0baa2ecc6256d038bdd9b56 or equivalent changes.
  • Identify routes or jobs passing user-controlled email values into the library.
  • Review monitoring for validation-related CPU spikes or availability degradation.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1333: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-25049 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
3CVSS 3.1LowCVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L1.51.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3Low
CVSS 3.1 vector shape for CVE-2018-25049Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aemail-existencen/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1333 · source CWE mapping

Inefficient Regular Expression Complexity

Inefficient Regular Expression Complexity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.