LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25074: Prestaul skeemas base.js redos

A vulnerability was found in Prestaul skeemas and classified as problematic. This issue affects some unknown processing of the file validators/base.js. The manipulation of the argument uri leads to inefficient regular expression complexity. The patch is named 65e94eda62dc8dc148ab3e59aa2ccc086ac448fd. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-218003.

LowCVSS 3.5Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2018-25074 is a low-severity denial-of-service risk in Prestaul skeemas. A URI validation path can trigger inefficient regular expression processing, potentially reducing availability. The sources do not identify affected versions, real-world exploitation, or business-impacting incidents.

Executive priority

Handle through normal vulnerability maintenance unless the dependency is present in exposed or multi-tenant workflows. The available evidence supports low urgency, focused on preventing localized availability degradation rather than data theft or system compromise.

Technical view

The issue is CWE-1333 in validators/base.js, where manipulation of the uri argument can cause inefficient regular expression complexity. CVSS 3.1 is 3.5 with adjacent attack vector, low attack complexity, low privileges required, no confidentiality or integrity impact, and low availability impact.

Likely exposure

Exposure is likely limited to applications using Prestaul skeemas and passing attacker-controlled URI values into the affected validator. The source bundle lists versions as n/a and provides no CPEs, so exact product exposure requires dependency review.

Exploitation context

The bundle does not show active exploitation, and KEV is false. The CVSS vector suggests an attacker needs adjacent access and low privileges, with impact limited to availability. No exploit details should be inferred beyond the described regex complexity condition.

Researcher notes

Key gaps are unspecified affected versions, no CPE data, and limited public technical detail beyond the affected file, uri argument, CWE-1333, and patch commit. Treat the patch as the strongest remediation signal and avoid claiming exploitation without new evidence.

Mitigation direction

  • Identify whether Prestaul skeemas is used in application dependencies.
  • Apply the upstream patch or a release containing commit 65e94eda62dc8dc148ab3e59aa2ccc086ac448fd.
  • If no packaged fix is available, check vendor guidance before carrying a local patch.
  • Reduce untrusted access to URI validation paths where practical.
  • Monitor affected services for abnormal validation latency or availability degradation.

Validation and detection

  • Review package manifests and lockfiles for Prestaul skeemas.
  • Confirm validators/base.js includes the referenced patch changes.
  • Map application paths that validate user-supplied uri values.
  • Verify dependency scanners recognize CVE-2018-25074 after remediation.
  • Record that affected versions are unspecified in the public sources.
Prepared
Confidence
medium
Sources
5

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-25074 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.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/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
4Source 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
3.5CVSS 3.1LowCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L2.11.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:A/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
Prestaulskeemasn/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.