{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.nifi.registry:nifi-registry-web-api. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-9482 in the wild and no public exploit code.","fix":"Upgrade org.apache.nifi.registry:nifi-registry-web-api to 0.7.0 or later.","what":"CVE-2020-9482 is a medium-severity vulnerability in Apache NiFi Registry, published on 28 Apr 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-9482 and fix it if it is affected.\n\nWhat it is: CVE-2020-9482 is a medium-severity vulnerability in Apache NiFi Registry, published on 28 Apr 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-9482 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.nifi.registry:nifi-registry-web-api (Maven): affected from 0.1.0; fixed in 0.7.0\n- org.apache.nifi.registry:nifi-registry-web-api (Maven): affected from 0.1.0; fixed in 0.7.0\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-9482/ (Markdown: https://insights.sbomify.com/CVE-2020-9482/index.md)","id":"CVE-2020-9482","markdown":"https://insights.sbomify.com/CVE-2020-9482/index.md","name":"CVE-2020-9482","record":{"aliases":["GHSA-rcwj-2hj2-vmjj"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Apache NiFi Registry","requires_auth":"none","summary":"Attackers can reuse client-side tokens for up to 12 hours after logout if non-PKI authentication is used, bypassing session invalidation.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"nifi_registry","vendor":"apache"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"If NiFi Registry 0.1.0 to 0.5.0 uses an authentication mechanism other than PKI, when the user clicks Log Out, NiFi Registry invalidates the authentication token on the client side but not on the server side. This permits the user's client-side token to be used for up to 12 hours after logging out to make API requests to NiFi Registry.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Insufficient Session Expiration in Apache NiFi Registry","id":"CVE-2020-9482","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":2,"n_references":1,"next":{"headline":"SQL injection in Apache SkyWalking","id":"CVE-2020-9483"},"packages":[{"ecosystem":"Maven","fixed":["0.7.0"],"introduced":["0.1.0"],"last_affected":[],"package":"org.apache.nifi.registry:nifi-registry-web-api","purl":null,"source":"GHSA-rcwj-2hj2-vmjj"},{"ecosystem":"Maven","fixed":["0.7.0"],"introduced":["0.1.0"],"last_affected":[],"package":"org.apache.nifi.registry:nifi-registry-web-api","purl":"pkg:maven/org.apache.nifi.registry/nifi-registry-web-api","source":"GHSA-rcwj-2hj2-vmjj"}],"prev":{"headline":"Denial of service in ATS","id":"CVE-2020-9481"},"products":["Apache NiFi Registry"],"published":"2020-04-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":["Apache"]},"summary":"Attackers can reuse client-side tokens for up to 12 hours after logout if non-PKI authentication is used, bypassing session invalidation.","url":"https://insights.sbomify.com/CVE-2020-9482/"}