{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-4099 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-4099 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-4099 is a medium-severity vulnerability in HCL Verse for Android, published on 1 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-4099 and fix it if it is affected.\n\nWhat it is: CVE-2020-4099 is a medium-severity vulnerability in HCL Verse for Android, published on 1 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-4099 in the wild and no public exploit code.\n\nAffected product: HCL Verse for Android. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-4099/ (Markdown: https://insights.sbomify.com/CVE-2020-4099/index.md)","id":"CVE-2020-4099","markdown":"https://insights.sbomify.com/CVE-2020-4099/index.md","name":"CVE-2020-4099","record":{"aliases":["GHSA-pc4m-vcwh-9c5h"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"HCL Verse Android app","requires_auth":"none","summary":"Attackers can forge digital signatures to distribute maliciously modified versions of the HCL Verse Android application due to weak signing keys.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"HCL","cpe":[{"product":"verse","vendor":"hcltech"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-326","name":"Inadequate Encryption Strength"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"HCL Verse for Android is susceptible to an APK signing key check vulnerability","id":"CVE-2020-4099","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Code injection in \"HCL Verse for Android\"","id":"CVE-2020-4100"},"packages":[],"prev":{"headline":"Memory corruption in HCL Notes","id":"CVE-2020-4097"},"products":["HCL Verse for Android"],"published":"2022-11-01","related":[{"cvss_score":8.3,"headline":"HCL Verse is susceptible to a Stored Cross-Site Scripting (XSS) Vulnerability","id":"CVE-2023-37496","kev_date_added":null,"published":"2023-08-01"},{"cvss_score":8.3,"headline":"HCL Verse is susceptible to a Cross Site Scripting (XSS) vulnerability","id":"CVE-2021-27788","kev_date_added":null,"published":"2023-03-10"},{"cvss_score":6.5,"headline":"HCL Verse is susceptible to a Reflected Cross-Site Scripting (XSS) Vulnerability","id":"CVE-2023-28013","kev_date_added":null,"published":"2023-07-26"},{"cvss_score":6.3,"headline":"An SSL certificate host verification vulnerability affects HCL Verse for Android","id":"CVE-2021-27768","kev_date_added":null,"published":"2022-05-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-02","vendors":["HCL Software"]},"summary":"Attackers can forge digital signatures to distribute maliciously modified versions of the HCL Verse Android application due to weak signing keys.","url":"https://insights.sbomify.com/CVE-2020-4099/"}