LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25079: Segmentio is-url index.js redos

A vulnerability was found in Segmentio is-url up to 1.2.2. 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 attack may be launched remotely. Upgrading to version 1.2.3 is able to address this issue. The patch is identified as 149550935c63a98c11f27f694a7c4a9479e53794. It is recommended to upgrade the affected component. VDB-220058 is the identifier assigned to this vulnerability.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability affects the npm package Segmentio is-url versions 1.2.0 through 1.2.2. Crafted input can make the package's regular expression work inefficiently, potentially slowing an application that uses it. The cited CVSS score is 4.3, with low availability impact and no confidentiality or integrity impact.

Executive priority

Treat this as a moderate dependency hygiene issue. It is not described as data theft or remote code execution, but it can affect availability where vulnerable versions process untrusted input. Prioritize normal patch cycles, faster for internet-facing services.

Technical view

CVE-2018-25079 is CWE-1333, inefficient regular expression complexity, in index.js of segmentio/is-url. The CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L. Sources identify version 1.2.3 and commit 149550935c63a98c11f27f694a7c4a9479e53794 as the patch.

Likely exposure

Exposure is most likely in Node.js applications that directly or transitively depend on segmentio/is-url versions 1.2.0, 1.2.1, or 1.2.2, especially where URL-like user input reaches this validator.

Exploitation context

The source bundle says the attack may be launched remotely, but the CVSS vector requires low privileges. The CVE is not listed as KEV in the bundle, and no cited source confirms active exploitation.

Researcher notes

Evidence identifies the affected package, vulnerable versions, CWE, CVSS vector, and patch. The bundle does not name specific downstream products, proof-of-concept status, or confirmed exploitation, so exposure assessment depends on local dependency and data-flow review.

Mitigation direction

  • Upgrade segmentio/is-url to version 1.2.3 or later.
  • Regenerate lockfiles so transitive dependency resolution actually changes.
  • Redeploy affected services after dependency updates are verified.
  • If upgrade is delayed, reduce untrusted input paths using this validator.
  • Monitor affected services for latency spikes or availability degradation.

Validation and detection

  • Search package manifests, lockfiles, and SBOMs for segmentio/is-url.
  • Confirm no deployed artifact resolves is-url to 1.2.0, 1.2.1, or 1.2.2.
  • Identify routes or jobs that pass user-controlled strings into URL validation.
  • Verify the deployed dependency includes the referenced patched release or commit.
  • Check dependency scanners after lockfile updates and redeployment.
Prepared
Confidence
high
Sources
7

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-25079 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
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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
6Source 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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2018-25079Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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
Segmentiois-url1.2.0, 1.2.1, 1.2.2Listed
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.