re2c records
3 published records for vendor re2c.
Researcher profile
- Entered KEV
- 0 · 0%
- Weaponized
- 0 · 0%
- Pre-auth RCE
- 0
- With a fix record
- 100%
- Median publish → KEV
- No record has entered KEV
Attack profile
All records
3 records| Action | CVE | Vulnerability | Severity | KEV | EPSS | Published |
|---|---|---|---|---|---|---|
39Monitor | CVE-2022-23901No exploit | A stack overflow re2c 2.2 exists due to infinite recursion issues in src/dfa/dead_rules.cc.re2c · re2c · CWE-787 | Critical9.8 | — | 1.5% | Mar 29, 2022 |
32Monitor | CVE-2020-11958No exploit | re2c 1.3 has a heap-based buffer overflow in Scanner::fill in parse/scanner.cc via a long lexeme.re2c · re2c · CWE-787 | High7.8 | — | 1.6% | Apr 20, 2020 |
22Monitor | CVE-2018-21232No exploit | re2c before 2.0 has uncontrolled recursion that causes stack consumption in find_fixed_tags.re2c · re2c · CWE-674 | Medium5.5 | — | 1.4% | Apr 29, 2020 |
- CVE-2022-2390139Monitor
A stack overflow re2c 2.2 exists due to infinite recursion issues in src/dfa/dead_rules.cc.
CriticalCVSS 9.8No exploitEPSS 1%re2c · re2cMar 29, 2022
- CVE-2020-1195832Monitor
re2c 1.3 has a heap-based buffer overflow in Scanner::fill in parse/scanner.cc via a long lexeme.
HighCVSS 7.8No exploitEPSS 1%re2c · re2cApr 20, 2020
- CVE-2018-2123222Monitor
re2c before 2.0 has uncontrolled recursion that causes stack consumption in find_fixed_tags.
MediumCVSS 5.5No exploitEPSS 1%re2c · re2cApr 29, 2020