OSV-2020-1820
Stack-buffer-overflow in hermes::regex::Parser<hermes::regex::Regex<hermes::regex::UTF16RegexTraits>, cha
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25815
Crash type: Stack-buffer-overflow READ 2
Crash state:
hermes::regex::Parser<hermes::regex::Regex<hermes::regex::UTF16RegexTraits>, cha
hermes::regex::Parser<hermes::regex::Regex<hermes::regex::UTF16RegexTraits>, cha
hermes::regex::Parser<hermes::regex::Regex<hermes::regex::UTF16RegexTraits>, cha
What each source reports
OSV No score
Stack-buffer-overflow in hermes::regex::Parser<hermes::regex::Regex<hermes::regex::UTF16RegexTraits>, cha
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25815
Crash type: Stack-buffer-overflow READ 2
Crash state:
hermes::regex::Parser<hermes::regex::Regex<hermes::regex::UTF16RegexTraits>, cha
hermes::regex::Parser<hermes::regex::Regex<hermes::regex::UTF16RegexTraits>, cha
hermes::regex::Parser<hermes::regex::Regex<hermes::regex::UTF16RegexTraits>, cha
- Record
OSV-2020-1820- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
hermesOSS-Fuzz |
Commit ranges | Not evaluated |
Not evaluated means the source gave git commits or a range we can't read, so we can't tell which releases are affected. A fixed version beside it is the source’s own claim.
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
OSV-2020-1820 is a vulnerability with no CVSS score yet in hermes, published September 21, 2020. No source lists public exploit code. A source reports a fix.