Skip to content
Fencer Intel
high 8.8

CVE-2018-12540 json

High severity vulnerability that affects io.vertx:vertx-web

published 8y ago modified 4mo ago also GHSA-rvgg-f8qm-6h7j , EUVD-2018-0690

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 80%
public exploits
0
none known

Summary

In version from 3.0.0 to 3.5.2 of Eclipse Vert.x, the CSRFHandler do not assert that the XSRF Cookie matches the returned XSRF header/form parameter. This allows replay attacks with previously issued tokens which are not expired yet.

Patch / fix

  • maven io.vertx:vertx-web 3.5.3

Is CVE-2018-12540 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

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-12540 updated cvss 6.8

vertx-web: Incomplete CSRF validation by CSRFHandler

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

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

Exploits and checks

  • access.redhat.com https://access.redhat.com/errata/RHSA-2018:2371 referenced PoC, tagged "exploit" by a source, unverified
  • bugs.eclipse.org https://bugs.eclipse.org/bugs/show_bug.cgi?id=536948 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected packages

ecosystem package affected fixed in
maven io.vertx:vertx-web
>=3.0.0, <3.5.3
3.5.3

Affected products

  • The Eclipse Foundation Eclipse Vert.x

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery

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.