CVE-2018-25007 json
Unauthorized client-side property update in UIDL request handler in Vaadin 10 and 11
published 5y ago modified 4mo ago also GHSA-jmx8-355m-8vwh , EUVD-2021-0842
- cvss
- 2.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 47%
- public exploits
- 0
- none known
Summary
Missing check in UIDL request handler in com.vaadin:flow-server versions 1.0.0 through 1.0.5 (Vaadin 10.0.0 through 10.0.7, and 11.0.0 through 11.0.2) allows attacker to update element property values via crafted synchronization message.
Patch / fix
- maven com.vaadin:flow-server 1.0.6
- vaadin flow 1.0.6
- vaadin vaadin 10.0.8, 11.0.3
- github.com/vaadin/flow#4774 pull request
Is CVE-2018-25007 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 FencerExploit prediction
0.57% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 2.6 | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N |
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:P/A:N |
| GitHub | 3.1 | 2.6 | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | com.vaadin:flow-server | >=1.0.0, <1.0.6 |
1.0.6 |
Affected products
- Vaadin Vaadin
- Vaadin flow-server
Classification
- Weakness
-
- CWE-754 Improper Check for Unusual or Exceptional Conditions
References
-
github.com
/vaadin/flow/pull/4774
web, patch, third-party-advisory
-
vaadin.com
/security/cve-2018-25007
web, vendor-advisory
-
github.com
/vaadin/flow/security/advisories/GHSA-jmx8-355m-8vwh
web
-
nvd.nist.gov
/vuln/detail/CVE-2018-25007
advisory
Sources
- CVE List CVE-2018-25007
- GitHub Advisory GHSA-jmx8-355m-8vwh
- NVD CVE-2018-25007
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.