GHSA-c99r-67x4-whj6 CVE-2021-33604
Reflected cross-site scripting in development mode handler in Vaadin 14, 15-19
Low
Maven
- Severity
- 2.5 / 10
- Low · CVSS 3.1
- Exploit chance (EPSS)
- 0.29%
- Chance of exploitation in the next 30 days. Higher than 21.13% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-172 Encoding Error
- Fix
14.6.2- Upgrade com.vaadin:vaadin-bom to this version or later
Description
URL encoding error in development mode handler in com.vaadin:flow-server versions 2.0.0 through 2.6.1 (Vaadin 14.0.0 through 14.6.1), 3.0.0 through 6.0.9 (Vaadin 15.0.0 through 19.0.8) allows local user to execute arbitrary JavaScript code by opening crafted URL in browser.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| com.vaadin:vaadin-bom | >= 14.0.0, < 14.6.2 |
14.6.2 |
| com.vaadin:vaadin-bom | >= 15.0.0, < 19.0.9 |
19.0.9 |
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 → 14.6.2
- maven
<dependency><groupId>com.vaadin</groupId><artifactId>vaadin-bom</artifactId><version>14.6.2</version></dependency>- gradle
implementation("com.vaadin:vaadin-bom:14.6.2")
Severity breakdown
CVSS 3.1 2.5
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Weakness
CWE-172: Encoding Error
The product does not properly encode or decode the data, resulting in unexpected values.
How to prevent it
- Implementation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
- Implementation: While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).
- Implementation: Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
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-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-75xc-qvxh-27f8 Timing side channel vulnerability in UIDL request handler in Vaadin 7 and 8 | 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