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.
Metrics
Affected Vendors & Products
| Vendors | Products |
|---|---|
| Apache |
|
No data.
No data.
Advisories
| Source | ID | Title |
|---|---|---|
 EUVD |
EUVD-2019-0665 | 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. |
 Github GHSA |
GHSA-fgmr-vx7c-5wj6 | Timing attack on HMAC signature comparison in Apache Tapestry |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
MITRE
Status: PUBLISHED
Assigner: apache
Published:
Updated: 2024-08-04T22:10:09.295Z
Reserved: 2019-03-26T00:00:00
Link: CVE-2019-10071
Vulnrichment
No data.
NVD
Status : Modified
Published: 2019-09-16T18:15:10.360
Modified: 2024-11-21T04:18:20.350
Link: CVE-2019-10071
Redhat
No data.
OpenCVE Enrichment
No data.