HCL Verse for Android is susceptible to an APK signing key check vulnerability

published 2022-11-01 4 y ago modified 2026-06-17 4 mo ago also EUVD-2020-25346

cvss: 5.9; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 30%
public exploits: 0; none known

The application was signed using a key length less than or equal to 1024 bits, making it potentially vulnerable to forged digital signatures. An attacker could forge the same digital signature of the app after maliciously modifying the app.

Patch / fix

fixed in 1

hcltech verse 12.0.15

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 18 mo ago (2025-05-02)

Exploit prediction

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

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.9	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected products

HCL Software HCL Verse for Android

Classification

Weakness

CWE-326 Inadequate Encryption Strength

References

support.hcltechsw.com /csm?id=kb_article&sysparm_article=KB0100861
vendor-advisory

Sources

CVE List CVE-2020-4099
NVD CVE-2020-4099

Fencer Vulns 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.

Summary