GHSA-c6c4-7x48-4cqp: Timing side channel vulnerability in UIDL request handler in Vaadin 10, 11-14, and 15-18
Noroxi assessment
Priority: Monitor (action score 16/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: com.vaadin:vaadin-bom (Maven) 10.0.17, 14.4.7, 18.0.6.
Low priority for now. Upgrade to com.vaadin:vaadin-bom (Maven) 10.0.17, 14.4.7, 18.0.6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: OSV
Non-constant-time comparison of CSRF tokens in UIDL request handler in `com.vaadin:flow-server` versions 1.0.0 through 1.0.13 (Vaadin 10.0.0 through 10.0.16), 1.1.0 prior to 2.0.0 (Vaadin 11 prior to 14), 2.0.0 through 2.4.6 (Vaadin 14.0.0 through 14.4.6), 3.0.0 prior to 5.0.0 (Vaadin 15 prior to 18), and 5.0.0 through 5.0.2 (Vaadin 18.0.0 through 18.0.5) allows attacker to guess a security token via timing attack. - https://vaadin.com/security/cve-2021-31404
- Published
- Apr 19, 2021
- Updated
- Dec 2, 2024
- EPSS
- —
- CWE
- CWE-208
Report tools
Action score
16
Low priority for now.
- CVSS
- 16 / 40 · 4.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| Maven | com.vaadin:vaadin-bom | pkg:maven/com.vaadin/vaadin-bom |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | com.vaadin:vaadin-bom | from 10.0.0 · before 10.0.17 | 10.0.17 |
| Maven | com.vaadin:vaadin-bom | from 11.0.0 · before 14.4.7 | 14.4.7 |
| Maven | com.vaadin:vaadin-bom | from 15.0.0 · before 18.0.6 | 18.0.6 |
Same product
Maven: all recordsOther highest-scoring records for the same primary product.
- GHSA-j9wr-49vq-rm5gServer classes and resources exposure in OSGi applications using Vaadin 12-14 and 1934Monitor
- GHSA-jfmf-w293-8xr8Regular expression Denial of Service (ReDoS) in EmailValidator class in V7 compatibility module in Vaadin 830Monitor
- GHSA-jqj4-r483-4gvrReflected cross-site scripting in default RouteNotFoundError view in Vaadin 10 and 11-1324Monitor
Published before and after this one in the same product
- ← EarlierGHSA-9h6g-6mxg-vvp4Apr 19, 2021 · Timing side channel vulnerability in endpoint request handler in Vaadin 15-1916Monitor
- Later →GHSA-82mf-mmh7-hxp5Apr 19, 2021 · Directory traversal in development mode handler in Vaadin 14 and 15-1723Monitor
- Later →GHSA-76f4-fw33-6j2vApr 19, 2021 · Potential sensitive data exposure in applications using Vaadin 1512Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:com.vaadin:vaadin-bom | 10.0.17 | Package registry (OSV) |
| Maven:com.vaadin:vaadin-bom | 14.4.7 | Package registry (OSV) |
| Maven:com.vaadin:vaadin-bom | 18.0.6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-208 · Observable Timing DiscrepancyCVSS vector
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
osv
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.