{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-24030 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-24030 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-24030 is a critical vulnerability in n/a, published on 2 Sep 2020. 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-24030 and fix it if it is affected.\n\nWhat it is: CVE-2020-24030 is a critical vulnerability in n/a, published on 2 Sep 2020. 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-24030 in the wild and no public exploit code.\n\nAffected product: n/a. 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-24030/ (Markdown: https://insights.sbomify.com/CVE-2020-24030/index.md)","id":"CVE-2020-24030","markdown":"https://insights.sbomify.com/CVE-2020-24030/index.md","name":"CVE-2020-24030","record":{"aliases":["GHSA-w553-m7x7-p3hj"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"ForLogic Qualiex","requires_auth":"none","summary":"Weak token expiration in ForLogic Qualiex allows remote unauthenticated privilege escalation and sensitive data access via token reuse.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"qualiex","vendor":"forlogic"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-672","name":"Operation on a Resource after Expiration or Release"}],"description":"ForLogic Qualiex v1 and v3 has weak token expiration. This allows remote unauthenticated privilege escalation and access to sensitive data via token reuse. NOTE: as of 2025-10-14, the Supplier's perspective is that this is \"not exploitable in the current implementation. Tokens are properly expired, invalidated, and bound to session context. Attempts to alter the token payload to extend its validity do not affect server-side validation.\"","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2020-08-31","github_poc":2,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-08-31T18:38:58Z","kind":"github_poc","ref":"https://github.com/underprotection/CVE-2020-24030","stars":0,"title":null},{"date":"2026-07-29T23:10:37Z","kind":"github_poc","ref":"https://github.com/RedTeamBrasil/CVE-2020-24030","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":null,"headline":"Weak cryptography in n/a","id":"CVE-2020-24030","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in n/a","id":"CVE-2020-24032"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2020-24029"},"products":["n/a"],"published":"2020-09-02","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2020-24029","kev_date_added":null,"published":"2020-09-02"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2020-24028","kev_date_added":null,"published":"2020-09-02"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2025-10-14","vendors":["n/a"]},"summary":"Weak token expiration in ForLogic Qualiex allows remote unauthenticated privilege escalation and sensitive data access via token reuse.","url":"https://insights.sbomify.com/CVE-2020-24030/"}