Skip to content
Fencer Intel
low 3.5

CVE-2023-25500 json

Vaadin vulnerable to possible information disclosure of class and method names in RPC response

published 3y ago modified 2mo ago also GHSA-ch48-9r3q-pv7x , EUVD-2023-1775

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

Summary

Possible information disclosure in Vaadin 10.0.0 to 10.0.23, 11.0.0 to 14.10.1, 15.0.0 to 22.0.28, 23.0.0 to 23.3.13, 24.0.0 to 24.0.6, 24.1.0.alpha1 to 24.1.0.rc2, resulting in potential information disclosure of class and method names in RPC responses by sending modified requests.

Patch / fix

  • maven com.vaadin:flow-server 1.0.21, 2.9.3, 9.1.2, 23.3.13, 24.0.9, 24.1.0
  • maven com.vaadin:vaadin 10.0.24, 14.10.2, 22.1.0, 23.3.14, 24.0.7, 24.1.0
  • vaadin vaadin 10.0.23, 14.10.2, 23.3.14, 24.0.7

Is CVE-2023-25500 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
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
CNA 3.1 3.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 3.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven com.vaadin:flow-server
>=1.0.0, <1.0.21
>=1.1.0, <2.9.3
>=3.0.0, <9.1.2
>=23.0.0, <23.3.13
>=24.0.0, <24.0.9
>=24.1.alpha1, <24.1.0
1.0.21
2.9.3
9.1.2
23.3.13
24.0.9
24.1.0
maven com.vaadin:vaadin
>=10.0.0, <10.0.24
>=11.0.0, <14.10.2
>=15.0.0, <22.1.0
>=23.0.0, <23.3.14
>=24.0.0, <24.0.7
>=24.1.0.alpha1, <24.1.0
10.0.24
14.10.2
22.1.0
23.3.14
24.0.7
24.1.0

Affected products

  • vaadin vaadin
  • flow flow-server

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-1295 Debug Messages Revealing Unnecessary Information

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.