LiveActive security incident?Get immediate response
CVE Record

CVE-2021-31405: Regular expression denial of service (ReDoS) in EmailField component in Vaadin 14 and 15-17

Unsafe validation RegEx in EmailField component in com.vaadin:vaadin-text-field-flow versions 2.0.4 through 2.3.2 (Vaadin 14.0.6 through 14.4.3), and 3.0.0 through 4.0.2 (Vaadin 15.0.0 through 17.0.10) allows attackers to cause uncontrolled resource consumption by submitting malicious email addresses.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This vulnerability lets an attacker make affected Vaadin applications spend excessive processing time validating specially crafted email input. The business impact is availability: public forms using Vaadin EmailField could become slow or unavailable without the attacker needing an account.

Executive priority

Treat this as a high-priority availability risk for affected public Vaadin applications. It is not a data theft issue, but it can disrupt customer-facing workflows if vulnerable forms are exposed.

Technical view

CVE-2021-31405 is a ReDoS issue in Vaadin EmailField validation. Affected com.vaadin:vaadin-text-field-flow versions are 2.0.4 through 2.3.2 and 3.0.0 through 4.0.2, corresponding to Vaadin 14.0.6-14.4.3 and 15.0.0-17.0.10. CVSS is 7.5, availability-only.

Likely exposure

Exposure is most likely in Java web applications using affected Vaadin versions with EmailField on public or unauthenticated forms, such as signup, contact, account recovery, or profile pages.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not listed as KEV. Exploitation requires submitting malicious email values to affected EmailField validation, causing uncontrolled resource consumption.

Researcher notes

The issue maps to CWE-400 and CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Evidence supports ReDoS in EmailField validation, but the bundle does not provide exploit payloads, operational indicators, or exact fixed version numbers.

Mitigation direction

  • Inventory Vaadin and vaadin-text-field-flow dependency versions across applications.
  • Upgrade affected Vaadin components according to Vaadin’s advisory and related fix PR.
  • Prioritize internet-facing forms that accept email addresses without authentication.
  • Apply rate limiting or request throttling where vulnerable forms cannot be upgraded quickly.
  • Monitor CPU saturation and slow requests around email-validation workflows.

Validation and detection

  • Confirm dependency trees do not include affected vaadin-text-field-flow ranges.
  • Identify routes and pages using Vaadin EmailField components.
  • Review APM and logs for abnormal CPU or latency on email form submissions.
  • Verify upgraded builds use vendor-fixed component versions.
  • Regression-test email forms for normal validation behavior after upgrade.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-31405 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2021-31405Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
VaadinVaadin14.0.6Listed
Vaadinvaadin-text-field-flow2.0.4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.