Skip to content
Fencer Intel
medium 4.3

CVE-2018-25031 json

Spoofing attack in swagger-ui

published 4y ago modified 4mo ago also GHSA-cr3q-pqgq-m8c2 , EUVD-2022-1408

cvss
4.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
42.3%
EPSS 42.3% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

Swagger UI 4.1.2 and earlier could allow a remote attacker to conduct spoofing attacks. By persuading a victim to open a crafted URL, an attacker could exploit this vulnerability to display remote OpenAPI definitions. Note: This was originally claimed to be resolved in 4.1.3. However, third parties have indicated this is not resolved in 4.1.3 and even occurs in that version and possibly others.

Patch / fix

  • npm swagger-ui 4.1.3
  • maven org.webjars:swagger-ui 4.1.3
  • smartbear swagger_ui 4.1.3

Is CVE-2018-25031 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

42.33% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
CNA 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N
GitHub 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm swagger-ui
<4.1.3
4.1.3
maven org.webjars:swagger-ui
<4.1.3
4.1.3

Affected products

  • smartbear swagger_ui

Classification

Weakness
  • CWE-922 Insecure Storage of Sensitive Information
  • CWE-918 Server-Side Request Forgery
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.