CVE-2022-27810
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIt was possible to trigger an infinite recursion condition in the error handler when Hermes executed specific maliciously formed JavaScript. This condition was only possible to trigger in dev-mode (when asserts were enabled). This issue affects Hermes versions prior to v0.12.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceHermes JavaScript engine contains an infinite recursion vulnerability in its error handler that can be triggered by specially crafted malicious JavaScript code. This issue only manifests in development mode when asserts are enabled, and affects all Hermes versions prior to v0.12.0.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.12.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Hermes versionCheck the Hermes library or binary version installed in your environment. This is typically found in the Hermes package metadata, library file properties, or by querying the Hermes runtime version if exposed in your application.Affected if The installed Hermes version is lower than 0.12.0 (e.g., 0.11.0, 0.10.0, etc.)
-
Determine if development mode is enabledInspect your build configuration, runtime environment variables, or application settings to determine whether Hermes is running in development mode. Look for flags such as HermesRuntimeConfig or similar development/debug mode settings.Affected if Development mode is explicitly enabled in the runtime configuration
-
Check if asserts are enabledReview your Hermes build configuration or runtime settings for assert/enable-assert flags. This may appear as a compile-time flag, runtime option, or build configuration setting that enables internal assertions.Affected if Asserts are enabled in the Hermes runtime configuration
You are affected if your Hermes version is below 0.12.0 AND development mode with asserts is currently enabled in your environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.12.0
Upgrade Hermes to version v0.12.0 or later, or ensure dev-mode with asserts is not enabled in production environments.
Hermes v0.12.0 or later
- Identify the current Hermes version in use by checking package.json or the bundled Hermes engine
- Upgrade Hermes to version 0.12.0 or later by updating the dependency in package.json (e.g., npm install [email protected] or latest)
- Rebuild/rebundle the JavaScript application to use the updated Hermes engine
- Verify the upgrade was successful by checking the Hermes version at runtime
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27810 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-27810 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data