How severe is CVE-2014-4671?

No CVSS score has been assigned to CVE-2014-4671 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-4671?

CVE-2014-4671 affects the following packages: hapi (npm). Ecosystems affected: npm.

How do I fix CVE-2014-4671?

Update hapi to 6.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-4671 is resolved across your whole dependency graph.

How do I detect CVE-2014-4671 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hapi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2014-4671 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.

Is CVE-2014-4671 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2014-4671, including 2 in-the-wild exploitations 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 is the EPSS score for CVE-2014-4671?

CVE-2014-4671 has an EPSS (Exploit Prediction Scoring System) score of 23.0%, placing it in the 98th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2014-4671?

CVE-2014-4671 is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-4671 published, and has it been updated?

CVE-2014-4671 was published on August 31, 2020 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2014-4671 — hapi

Fix: spumko/hapi#1766

CVE-2014-4671 is a Cross-Site Request Forgery (CSRF) vulnerability in hapi. 2 public exploit references exist, so weaponization risk is real. A fix is available for hapi — see the affected versions and patch details below.

Rosetta-Flash JSONP Vulnerability in hapi

Published

Aug 31, 2020

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

23.0%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

hapinpm

57Kdownloads / week

Description

This description taken from the pull request provided by Patrick Kettner.

Versions 6.1.0 and earlier of hapi are vulnerable to a rosetta-flash attack, which can be used by attackers to send data across domains and break the browser same-origin-policy.

Recommendation

Update hapi to version 6.1.1 or later.

Alternatively, a solution previously implemented by Google, Facebook, and Github is to prepend callbacks with an empty inline comment. This will cause the flash parser to break on invalid inputs and prevent the issue, and how the issue has been resolved internally in hapi.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`hapi`	all versions	6.1.0`npm install hapi@6.1.0`

Affected Products

3 products · 40 configurations

Application

adobe airadobe

≤ 14.0.0.110

2 versions

13.0.0.8313.0.0.111

Application

adobe air sdkadobe

≤ 14.0.0.110

2 versions

13.0.0.8313.0.0.111

Application

flash playeradobe

≤ 13.0.0.223

32 versions

11.2.202.22311.2.202.22811.2.202.23311.2.202.23511.2.202.23611.2.202.23811.2.202.24311.2.202.25111.2.202.25811.2.202.26111.2.202.26211.2.202.270

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.

Adobe Flash Player before 13.0.0.231 and 14.x before 14.0.0.145 on Windo…

miki.itNVDSep 2015

Adobe Flash Player before 13.0.0.231 and 14.x before 14.0.0.145 on Windo…

github.comMetasploitOct 2020

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hapi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update hapi to 6.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-4671 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Supplementary for Red Hat Enterprise Linux 5	`flash-plugin-0:11.2.202.394-1.el5`	RHSA-2014:0860

Frequently Asked Questions

This description taken from the pull request provided by Patrick Kettner. Versions 6.1.0 and earlier of hapi are vulnerable to a rosetta-flash attack, which can be used by attackers to send data across domains and break the browser same-origin-policy. ## Recommendation - Update hapi to version 6.1.1 or later. Alternatively, a solution previously implemented by Google, Facebook, and Github is to prepend callbacks with an empty inline comment. This will cause the flash parser to break on invalid inputs and prevent the issue, and how the issue has been resolved internally in hapi.

O3 Security · Impact-Aware SCA

Is CVE-2014-4671 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2014-4671 — hapi

EPSS Exploitation Probability

Real-World Exposure

Description

Recommendation

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2014-4671 in your dependencies?