CVE-2014-1972 json
Apache Tapestry Unsafe Object Storage
published 2015-08-22 11 y ago modified 2026-06-17 4 mo ago also GHSA-c438-8cvq-pxxx , EUVD-2022-3496
- cvss
- 7.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 9.6%
- EPSS 9.6% chance of exploitation in 30 days, percentile 95%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Exploit prediction
9.60% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.8 | AV:N/AC:L/Au:N/C:N/I:N/A:C |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.tapestry:tapestry-core | <5.3.6 |
5.3.6 |
Classification
References
-
github.com
/apache/tapestry-5/commit/5ad5257fdfacbad2c7c480fdf2afa15d9a37e6b0
web
-
tapestry.apache.org
/release-notes-536.html
web, vendor-advisory
-
jvn.jp
/en/jp/JVN17611367/index.html
third-party-advisory, web, vendor-advisory
-
jvndb.jvn.jp
/jvndb/JVNDB-2015-000118
third-party-advisory, web, vendor-advisory
-
issues.apache.org
/jira/browse/TAP5-2008
web
-
openwall.com
/lists/oss-security/2019/08/23/5
mailing-list, web
-
seclists.org
/fulldisclosure/2019/Aug/20
mailing-list, web
-
lists.apache.org
/thread.html/84e99dedad2ecb4676de93c3ab73a8a10882951ab6984f514707f3d9%40%3Cusers.tapestry.apache.org%3E
mailing-list
-
lists.apache.org
/thread.html/bac8d6f9e1b4059b319d9cba6f33219a99b81623476ec896138f851c%40%3Cusers.tapestry.apache.org%3E
mailing-list
-
lists.apache.org
/thread.html/r87523dd07886223aa086edc25fe9b8ddb9c1090f7db25b068dc30843%40%3Ccommits.tapestry.apache.org%3E
mailing-list
-
lists.apache.org
/thread.html/r7d9c54beb1dc97dcccc58d9b5d31f0f7166f9a25ad1beba5f8091e0c%40%3Ccommits.tapestry.apache.org%3E
mailing-list
-
nvd.nist.gov
/vuln/detail/CVE-2014-1972
advisory
-
github.com
/apache/tapestry-5
web
-
lists.apache.org
/thread.html/84e99dedad2ecb4676de93c3ab73a8a10882951ab6984f514707f3d9@%3Cusers.tapestry.apache.org%3E
web
-
lists.apache.org
/thread.html/bac8d6f9e1b4059b319d9cba6f33219a99b81623476ec896138f851c@%3Cusers.tapestry.apache.org%3E
web
-
lists.apache.org
/thread.html/r7d9c54beb1dc97dcccc58d9b5d31f0f7166f9a25ad1beba5f8091e0c@%3Ccommits.tapestry.apache.org%3E
web
-
lists.apache.org
/thread.html/r87523dd07886223aa086edc25fe9b8ddb9c1090f7db25b068dc30843@%3Ccommits.tapestry.apache.org%3E
web
Sources
- CVE List CVE-2014-1972
- GitHub Advisory GHSA-c438-8cvq-pxxx
- NVD CVE-2014-1972
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.