GHSA-75xc-qvxh-27f8 CVE-2021-31403
Timing side channel vulnerability in UIDL request handler in Vaadin 7 and 8
- Severity
- 4.0 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.31%
- Chance of exploitation in the next 30 days. Higher than 23.39% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Fix
- Available
- 2 packages have a fixed version
Description
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
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| com.vaadin:vaadin-bom | >= 7.0.0, < 7.7.24 |
7.7.24 |
| com.vaadin:vaadin-bom | >= 8.0.0, < 8.12.3 |
8.12.3 |
| com.vaadin:vaadin-server | >= 7.0.0, < 7.7.24 |
7.7.24 |
| com.vaadin:vaadin-server | >= 8.0.0, < 8.12.3 |
8.12.3 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
com.vaadin:vaadin-bom Maven → 7.7.24
- maven
<dependency><groupId>com.vaadin</groupId><artifactId>vaadin-bom</artifactId><version>7.7.24</version></dependency>- gradle
implementation("com.vaadin:vaadin-bom:7.7.24")
com.vaadin:vaadin-server Maven → 7.7.24
- maven
<dependency><groupId>com.vaadin</groupId><artifactId>vaadin-server</artifactId><version>7.7.24</version></dependency>- gradle
implementation("com.vaadin:vaadin-server:7.7.24")
Severity breakdown
CVSS 3.1 4.0
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
Weakness
CWE-203: Observable Discrepancy
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.
How to prevent it
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
- Implementation: Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success. If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files. Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.
CWE-208: Observable Timing Discrepancy
Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not.
References
Advisories
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-93c4-vf86-3rj7 Reflected cross-site scripting in vaadin-menu-bar webjar resources in Vaadin 14 | Medium | Also affects com.vaadin:vaadin-bom |
| GHSA-jfmf-w293-8xr8 Regular expression Denial of Service (ReDoS) in EmailValidator class in V7 compatibility module in Vaadin 8 | High | Also affects com.vaadin:vaadin-bom |
| GHSA-hw7r-qrhp-5pff Unauthorized property update in CheckboxGroup component in Vaadin 12-14 and 15-20 | Medium | Also affects com.vaadin:vaadin-bom |
| GHSA-c99r-67x4-whj6 Reflected cross-site scripting in development mode handler in Vaadin 14, 15-19 | Low | Also affects com.vaadin:vaadin-bom |
| GHSA-qrg9-f472-qwfm Possible route enumeration in production mode via RouteNotFoundError view in Vaadin 10, 11-14, and 15-19 | Medium | Also affects com.vaadin:vaadin-bom |
| GHSA-p826-8vhq-h439 Insecure temporary directory usage in frontend build functionality of Vaadin 14 and 15-19 | Medium | Also affects com.vaadin:vaadin-bom |
| GHSA-mr8h-j9cv-4m8h Server session is not invalidated when logout() helper method of Authentication module is used in Vaadin 18-19 | Medium | Also affects com.vaadin:vaadin-bom |
| GHSA-q74r-4xw3-ppx9 Stored cross-site scripting in Grid component in Vaadin 7 and 8 | Medium | Also affects com.vaadin:vaadin-bom |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor