{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-8434 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-8434 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-8434 is a critical vulnerability in n/a, published on 19 May 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-8434 and fix it if it is affected.\n\nWhat it is: CVE-2020-8434 is a critical vulnerability in n/a, published on 19 May 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-8434 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-8434/ (Markdown: https://insights.sbomify.com/CVE-2020-8434/index.md)","id":"CVE-2020-8434","markdown":"https://insights.sbomify.com/CVE-2020-8434/index.md","name":"CVE-2020-8434","record":{"aliases":["GHSA-xxqg-cq6p-jpqq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenzabar JICS","requires_auth":"none","summary":"Attackers can impersonate any user by generating valid session cookies using a hard-coded key, bypassing authentication and MFA in Jenzabar JICS.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"internet_campus_solution","vendor":"jenzabar"}],"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-384","name":"Session Fixation"}],"description":"Jenzabar JICS (aka Internet Campus Solution) before 9.0.1 Patch 3, 9.1 before 9.1.2 Patch 2, and 9.2 before 9.2.2 Patch 8 has session cookies that are a deterministic function of the username. There is a hard-coded password to supply a PBKDF feeding into AES to encrypt a username and base64 encode it to a client-side cookie for persistent session authentication. By knowing the key and algorithm, an attacker can select any username, encrypt it, base64 encode it, and save it in their browser with the correct JICSLoginCookie cookie format to impersonate any real user in the JICS database without the need for authenticating (or verifying with MFA if implemented).","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":"Hardcoded credentials in n/a","id":"CVE-2020-8434","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2020-8435"},"packages":[],"prev":{"headline":"Use after free in n/a","id":"CVE-2020-8432"},"products":["n/a"],"published":"2020-05-19","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2019-10011","kev_date_added":null,"published":"2019-03-25"},{"cvss_score":7.5,"headline":"File upload in n/a","id":"CVE-2019-10012","kev_date_added":null,"published":"2019-03-25"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can impersonate any user by generating valid session cookies using a hard-coded key, bypassing authentication and MFA in Jenzabar JICS.","url":"https://insights.sbomify.com/CVE-2020-8434/"}