Skip to content
Fencer Intel
critical 9.8

CVE-2019-0195 in the critical feed json

Deserialization of Untrusted Data in Apache Tapestry

published 7y ago modified 4mo ago also GHSA-6mwh-fw4p-75fj , EUVD-2022-2830

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
14.0%
EPSS 14.0% chance of exploitation in 30 days, percentile 96%
public exploits
0
none known

Summary

Manipulating classpath asset file URLs, an attacker could guess the path to a known file in the classpath and have it downloaded. If the attacker found the file with the value of the tapestry.hmac-passphrase configuration symbol, most probably the webapp's AppModule class, the value of this symbol could be used to craft a Java deserialization attack, thus running malicious injected Java code. The vector would be the t:formdata parameter from the Form component.

Patch / fix

  • maven org.apache.tapestry:tapestry-core 5.4.5

Is CVE-2019-0195 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

14.02% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.tapestry:tapestry-core
>=5.4.0, <5.4.5
5.4.5

Affected products

  • n/a Apache Tapestry

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

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.