GHSA-42j4-733x-5vcf CVE-2020-36320
Regular expression denial of service (ReDoS) in EmailValidator class in Vaadin 7
High
Maven
- Severity
- 7.5 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 1.96%
- Chance of exploitation in the next 30 days. Higher than 80.28% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-400 Uncontrolled Resource Consumption
- Fix
- Available
- 2 packages have a fixed version
Description
Unsafe validation RegEx in EmailValidator class in com.vaadin:vaadin-server versions 7.0.0 through 7.7.21 (Vaadin 7.0.0 through 7.7.21) allows attackers to cause uncontrolled resource consumption by submitting malicious email addresses.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| com.vaadin:vaadin-bom | >= 7.0.0.beta1, < 7.7.22 |
7.7.22 |
| com.vaadin:vaadin-server | >= 7.0.0.beta1, < 7.7.22 |
7.7.22 |
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.22
- maven
<dependency><groupId>com.vaadin</groupId><artifactId>vaadin-bom</artifactId><version>7.7.22</version></dependency>- gradle
implementation("com.vaadin:vaadin-bom:7.7.22")
com.vaadin:vaadin-server Maven → 7.7.22
- maven
<dependency><groupId>com.vaadin</groupId><artifactId>vaadin-server</artifactId><version>7.7.22</version></dependency>- gradle
implementation("com.vaadin:vaadin-server:7.7.22")
Severity breakdown
CVSS 3.1 7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Weakness
CWE-400: Uncontrolled Resource Consumption
The product does not properly control the allocation and maintenance of a limited resource.
How to prevent it
- Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
- Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
- Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
- Implementation: Ensure that all failures in resource allocation place the system into a safe posture.
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-75xc-qvxh-27f8 Timing side channel vulnerability in UIDL request handler 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