CVE-2018-25031
Vendor not named in the CVE record
Exploitation: likely to be exploited (10% or more)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 98% of scored CVEs
DescriptionCVE.org
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.
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Likely to be exploited (10% or more). EPSS gives it a 10% or higher chance of exploitation in the next 30 days.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Published
- March 2022
CoverageNo articles yet
No CyberSIXT article names CVE-2018-25031 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-922cwe.mitre.org
- security.snyk.io/vuln/SNYK-JS-SWAGGERUI-2314885security.snyk.io
- github.com/swagger-api/swagger-ui/issues/4872github.com
- github.com/swagger-api/swagger-ui/releases/tag/v4.1.3github.com
- security.netapp.com/advisory/ntap-20220407-0004security.netapp.com