CVE-2024-47073
Published: 07 November 2024
Summary
CVE-2024-47073 is a critical-severity Improper Verification of Cryptographic Signature (CWE-347) vulnerability in Dataease Dataease. Its CVSS base score is 9.3 (Critical).
Operationally, ranked in the top 1.9% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
DataEase, an open source data visualization analysis tool, contains CVE-2024-47073 in versions prior to 2.10.2. The flaw is the absence of JWT signature verification, which is tracked as CWE-347 and produces a CVSS 4.0 score of 9.3.
An unauthenticated network attacker can forge valid JWTs and thereby reach any application interface, resulting in high confidentiality and integrity impact without needing privileges or user interaction.
The GitHub Security Advisory states that the issue is resolved in release 2.10.2 and explicitly advises all users to upgrade, as no workarounds exist.
The associated EPSS score stands at 0.5611 with an identical peak value.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-42755
Vulnerability details
DataEase is an open source data visualization analysis tool that helps users quickly analyze data and gain insights into business trends. In affected versions a the lack of signature verification of jwt tokens allows attackers to forge jwts which then…
more
allow access to any interface. The vulnerability has been fixed in v2.10.2 and all users are advised to upgrade. There are no known workarounds for this vulnerability.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Requires verification of digital signatures using organization-approved certificates before installation, directly preventing improper verification of cryptographic signatures.
Component authenticity commonly depends on cryptographic signatures; the control enforces proper verification of those signatures.
PKI certificates under an approved policy require cryptographic signature verification on issuance and validation.
Requires cryptographic signatures on authoritative data and support for verifying the chain of trust.
Mandates verification of cryptographic signatures (e.g., DNSSEC RRSIG) on resolution responses, addressing missing or bypassed signature checks.
Integrity tools commonly rely on cryptographic signatures whose improper validation this weakness covers.
Authenticity validation commonly relies on cryptographic signature or certificate checks that this control enforces.