How severe is CVE-2014-1972?

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

Which packages are affected by CVE-2014-1972?

CVE-2014-1972 affects the following packages: org.apache.tapestry:tapestry-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2014-1972?

Update org.apache.tapestry:tapestry-core to 5.3.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-1972 is resolved across your whole dependency graph.

How do I detect CVE-2014-1972 in my Maven dependencies?

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

How do I mitigate CVE-2014-1972 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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

No public exploit code has been indexed for CVE-2014-1972 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2014-1972?

CVE-2014-1972 has an EPSS (Exploit Prediction Scoring System) score of 9.6%, placing it in the 95th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2014-1972?

CVE-2014-1972 is classified as CWE-399 (CWE-399). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2014-1972 was published on May 13, 2022 and was last updated on December 8, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2014-1972 — tapestry-core

Fix: apache/tapestry-5@5ad5257

CVE-2014-1972 is a CWE-399 vulnerability in org.apache.tapestry:tapestry-core. A fix is available for org.apache.tapestry:tapestry-core — see the affected versions and patch details below.

Apache Tapestry Unsafe Object Storage

Published

May 13, 2022

Updated

Dec 8, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

9.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕org.apache.tapestry:tapestry-core

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

Description

Apache Tapestry before 5.3.6 relies on client-side object storage without checking whether a client has modified an object, which allows remote attackers to cause a denial of service (resource consumption) or execute arbitrary code via crafted serialized data.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tapestry:tapestry-core`	all versions	5.3.6`org.apache.tapestry:tapestry-core:5.3.6`

Affected Products

1 product · 1 configurations

Application

tapestryapache

≤ 5.3.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tapestry:tapestry-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tapestry:tapestry-core to 5.3.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-1972 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-1972 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works