How severe is GHSA-34r7-q49f-h37c?

GHSA-34r7-q49f-h37c has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-34r7-q49f-h37c?

GHSA-34r7-q49f-h37c affects the following packages: uglify-js (npm), uglifier (RubyGems). Ecosystems affected: npm, RubyGems.

How do I fix GHSA-34r7-q49f-h37c?

Update uglify-js to 2.4.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-34r7-q49f-h37c is resolved across your whole dependency graph.

How do I detect GHSA-34r7-q49f-h37c in my npm, RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for uglify-js. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-34r7-q49f-h37c if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-34r7-q49f-h37c?

O3 pinpoints whether GHSA-34r7-q49f-h37c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-34r7-q49f-h37c actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-34r7-q49f-h37c, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is GHSA-34r7-q49f-h37c?

GHSA-34r7-q49f-h37c is classified as CWE-254 (CWE-254). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-34r7-q49f-h37c published, and has it been updated?

GHSA-34r7-q49f-h37c was published on October 24, 2017 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm💎 RubyGems

GHSA-34r7-q49f-h37c

CRITICAL

Incorrect Handling of Non-Boolean Comparisons During Minification in uglify-js

Also known asCVE-2015-8857

Published

Oct 24, 2017

Updated

Feb 16, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

Blast Radius

2 pkgs affected

📦uglify-js💎uglifier

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm, RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

Versions of uglify-js prior to 2.4.24 are affected by a vulnerability which may cause crafted JavaScript to have altered functionality after minification.

Recommendation

Upgrade UglifyJS to version >= 2.4.24.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`uglify-js`	all versions	2.4.24
💎RubyGems	`uglifier`	all versions	2.7.2

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The uglify-js package before 2.4.24 for Node.js does not properly accoun…

nodesecurity.ioNVDDec 2019

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for uglify-js. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update uglify-js to 2.4.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-34r7-q49f-h37c is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-34r7-q49f-h37c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-34r7-q49f-h37c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `uglify-js` prior to 2.4.24 are affected by a vulnerability which may cause crafted JavaScript to have altered functionality after minification. ## Recommendation Upgrade UglifyJS to version >= 2.4.24.

O3 Security · Impact-Aware SCA

Is GHSA-34r7-q49f-h37c in your dependencies?

O3 detects GHSA-34r7-q49f-h37c across npm, RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works