Skip to content
Fencer Vulns
medium 5.3

CVE-2018-12537 json

Moderate severity vulnerability that affects io.vertx:vertx-core

published 2018-08-14 8 y ago modified 2026-06-17 4 mo ago also GHSA-6cw8-7j6c-hccp , EUVD-2018-0516

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

Summary

In Eclipse Vert.x version 3.0 to 3.5.1, the HttpServer response headers and HttpClient request headers do not filter carriage return and line feed characters from the header value. This allow unfiltered values to inject a new header in the client request or server response.

Patch / fix

  • maven io.vertx:vertx-core 3.5.2

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-12537 updated cvss 5.3

vertx: Improper neutralization of CRLF sequences allows remote attackers to inject arbitrary HTTP response headers

  • Red Hat Fuse 7.2
    fixed: vendor fix RHSA-2018:3768
  • Red Hat Text-Only RHOAR
    fixed: vendor fix RHSA-2018:2371
  • Red Hat JBoss Fuse 6 vertx vertx
    not affected: vulnerable code not present

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

2.48% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N

Affected packages

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

Affected products

  • The Eclipse Foundation Eclipse Vert.x

Classification

Weakness
  • CWE-93 Improper Neutralization of CRLF Sequences
  • CWE-20 Improper Input Validation

References

Sources

Fencer Vulns 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.