CVE-2019-10071GHSA-FGMR-VX7C-5WJ6
The code which checks HMAC in form submissions used String.equals() for comparisons, which results in a timing side channel for the comparis
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.4.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The code which checks HMAC in form submissions used String.equals() for comparisons, which results in a timing side channel for the comparison of the HMAC signatures. This could lead to remote code execution if an attacker is able to determine the correct signature for their payload. The comparison should be done with a constant time algorithm instead.
Timeline
- CVE published
- Record last updated
Affected versions
- Apache Apache Tapestry
Apache Tapestry 5.4.0 to 5.4.3
- org.apache.tapestry:tapestry-coreMaven
From 5.4 · fixed in 5.4.5
References 5
lists.apache.org
- thread.html/6e8f42c88da7be3c60aafe3f6a85eb00b4f8b444de26b38d36233a43@<users.tapestry.apache.org>
- thread.html/bac8d6f9e1b4059b319d9cba6f33219a99b81623476ec896138f851c@<users.tapestry.apache.org>
- thread.html/7a437dad5af7309aba4d01bfc2463b3ac34e6aafaa565381d3a36460@<users.tapestry.apache.org>
- thread.html/r87523dd07886223aa086edc25fe9b8ddb9c1090f7db25b068dc30843@<commits.tapestry.apache.org>
- thread.html/r7d9c54beb1dc97dcccc58d9b5d31f0f7166f9a25ad1beba5f8091e0c@<commits.tapestry.apache.org>