CVE-2021-31403: Timing side channel vulnerability in UIDL request handler in Vaadin 7 and 8
Noroxi assessment
Priority: Monitor (action score 10/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: com.vaadin:vaadin-bom (Maven) 7.7.24, 8.12.3; com.vaadin:vaadin-server (Maven) 7.7.24, 8.12.3.
Low priority for now. Upgrade to com.vaadin:vaadin-bom (Maven) 7.7.24, 8.12.3; com.vaadin:vaadin-server (Maven) 7.7.24, 8.12.3 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: NVD · CVE.org · FIRST EPSS
Non-constant-time comparison of CSRF tokens in UIDL request handler in com.vaadin:vaadin-server versions 7.0.0 through 7.7.23 (Vaadin 7.0.0 through 7.7.23), and 8.0.0 through 8.12.2 (Vaadin 8.0.0 through 8.12.2) allows attacker to guess a security token via timing attack
- Published
- Apr 23, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 23th percentile
- CWE
- CWE-208
Report tools
Action score
10
Monitor
Low priority for now.
- CVSS
- 10 / 40 · 2.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CNA vs NVD score
- NVD
- 2.5
- CNA · Vaadin
- 4.0
- 1.5 point gap
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
|---|---|---|
| vaadin | vaadin | cpe:2.3:a:vaadin:vaadin |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- vaadin vaadin7.0.0 and later · before 7.7.24
- vaadin vaadin8.0.0 and later · before 8.12.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Vaadin). Independent of NVD's CPE analysis and usually ahead of it.
Vaadin Vaadin
- 7.0.0 and lateraffected
Vaadin vaadin-server
- 7.0.0 and lateraffected
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 7.0.0 · before 7.7.24 | 7.7.24 |
| Maven | com.vaadin:vaadin-bom | from 8.0.0 · before 8.12.3 | 8.12.3 |
| Maven | com.vaadin:vaadin-server | from 7.0.0 · before 7.7.24 | 7.7.24 |
| Maven | com.vaadin:vaadin-server | from 8.0.0 · before 8.12.3 | 8.12.3 |
Same product
vaadin: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-107588Multiple Vulnerabilities in the Highcharts Library Bundled with Vaadin Charts33Monitor
- CVE-2021-31409Server session is not invalidated when logout() helper method of Authentication module is used in Vaadin 18-1931Monitor
- CVE-2020-36320Regular expression Denial of Service (ReDoS) in EmailValidator class in Vaadin 731Monitor
Published before and after this one in the same product
- ← EarlierCVE-2011-0509Jan 20, 2011 · Cross-site scripting (XSS) vulnerability in Vaadin before 6.4.9 allows remote attackers to inject arbitrary web script or HTML via unknown v18Monitor
- ← EarlierCVE-2019-25028Apr 23, 2021 · Stored cross-site scripting in Grid component in Vaadin 7 and 824Monitor
- Later →CVE-2021-33609Oct 13, 2021 · Denial of service in DataCommunicator class in Vaadin 817Monitor
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 | 7.7.24 | Package registry (OSV) |
| Maven:com.vaadin:vaadin-bom | 8.12.3 | Package registry (OSV) |
| Maven:com.vaadin:vaadin-server | 7.7.24 | Package registry (OSV) |
| Maven:com.vaadin:vaadin-server | 8.12.3 | 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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-208 · Observable Timing DiscrepancyCVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
nvd-primary
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
- 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.