dbcve.org
TapestryApplication · Apache

CVE-2019-0195

CRITICAL · 9.8 CVSS v3.1 Published 2019-09-16
Fix available
A fix is available. Upgrade to after 5.4.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Tapestry allows attackers to manipulate classpath asset file URLs to discover and download known files. If the attacker locates the file containing the tapestry.hmac-passphrase configuration symbol (typically in AppModule), they can obtain this value and craft a malicious Java deserialization attack via the t:formdata parameter in the Form component.

MitigationUpgrade Apache Tapestry to a patched version and ensure the tapestry.hmf-passphrase is not exposed in publicly accessible classpath files such as AppModule.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TapestryApplication
Affected:>= 5.4.0, <= 5.4.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Tapestry version
    Check your application's dependencies: examine the pom.xml for tapestry-core version, or locate tapestry-core-X.X.X.jar in WEB-INF/lib and note the version number from the filename
    Affected if The installed version is 5.4.0, 5.4.1, 5.4.2, or 5.4.3
  2. Confirm classpath asset serving is active
    Search your application code for usage of classpath: asset URLs, or check if the tapestry.asset.path.prefix configuration is set to a non-empty value in your application properties
    Affected if Classpath assets are being served publicly without access restrictions
  3. Locate tapestry.hmac-passphrase in source
    Search your Java source files (particularly AppModule.java or any configuration class) for the string 'tapestry.hmac-passphrase' to see if this configuration symbol is defined
    Affected if The hmac-passphrase value exists in a publicly accessible classpath file (such as AppModule) that could be downloaded via asset URL manipulation
  4. Verify Form component usage with t:formdata
    Search your Tapestry template files (.tml) for components using t:formdata parameter, or check if your forms reference the Form component's data binding that uses HMAC serialization
    Affected if The Form component with t:formdata parameter is in use, allowing crafted deserialization payloads if the hmac-passphrase is obtained

You are affected if your Tapestry version is 5.4.0-5.4.3 AND classpath assets are exposed AND the hmac-passphrase is in a downloadable classpath file AND the Form component with t:formdata is used.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 5.4.3
Interim mitigation

Upgrade Apache Tapestry to a patched version and ensure the tapestry.hmf-passphrase is not exposed in publicly accessible classpath files such as AppModule.

Recommended fix High confidence

Apache Tapestry 5.4.4

  1. Upgrade Apache Tapestry from version 5.4.0-5.4.3 to version 5.4.4 or later
  2. After upgrading, verify the application compiles and runs correctly
  3. Test all Form component functionality to ensure the application works as expected after the upgrade
Caveat Minor release upgrade within 5.4.x branch; should have minimal breaking changes, but test thoroughly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tapestry Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-0195 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-0195 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data