{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.ozone:ozone-main. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-36372 in the wild and no public exploit code.","fix":"Upgrade org.apache.ozone:ozone-main to 1.2.0 or later.","what":"CVE-2021-36372 is a critical vulnerability in Apache Ozone, published on 19 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-36372 and fix it if it is affected.\n\nWhat it is: CVE-2021-36372 is a critical vulnerability in Apache Ozone, published on 19 Nov 2021. 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-2021-36372 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.ozone:ozone-main (Maven): affected all versions; fixed in 1.2.0\n- org.apache.ozone:ozone-main (Maven): affected all versions; fixed in 1.2.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-2021-36372/ (Markdown: https://insights.sbomify.com/CVE-2021-36372/index.md)","id":"CVE-2021-36372","markdown":"https://insights.sbomify.com/CVE-2021-36372/index.md","name":"CVE-2021-36372","record":{"aliases":["GHSA-86fh-j58m-7pf5"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Ozone storage","requires_auth":"none","summary":"Authenticated users can retain access to data via persisted block tokens even after permissions are revoked in Apache Ozone.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"ozone","vendor":"apache"}],"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-273","name":"Improper Check for Dropped Privileges"}],"description":"In Apache Ozone versions prior to 1.2.0, Initially generated block tokens are persisted to the metadata database and can be retrieved with authenticated users with permission to the key. Authenticated users may use them even after access is revoked.","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":"Original block tokens are persisted and can be retrieved","id":"CVE-2021-36372","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2021"},"n_packages":2,"n_references":2,"next":{"headline":"Apache Ant TAR archive denial of service vulnerability","id":"CVE-2021-36373"},"packages":[{"ecosystem":"Maven","fixed":["1.2.0"],"introduced":["0"],"last_affected":[],"package":"org.apache.ozone:ozone-main","purl":null,"source":"GHSA-86fh-j58m-7pf5"},{"ecosystem":"Maven","fixed":["1.2.0"],"introduced":["0"],"last_affected":[],"package":"org.apache.ozone:ozone-main","purl":"pkg:maven/org.apache.ozone/ozone-main","source":"GHSA-86fh-j58m-7pf5"}],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2021-36371"},"products":["Apache Ozone"],"published":"2021-11-19","related":[{"cvss_score":9.1,"headline":"Missing authentication/authorization on internal RPC endpoints","id":"CVE-2021-39231","kev_date_added":null,"published":"2021-11-19"},{"cvss_score":9.1,"headline":"Container-related datanode operations can be called without authorization","id":"CVE-2021-39233","kev_date_added":null,"published":"2021-11-19"},{"cvss_score":8.8,"headline":"Missing admin check for SCM related admin commands","id":"CVE-2021-39232","kev_date_added":null,"published":"2021-11-19"},{"cvss_score":8.8,"headline":"Owners of the S3 tokens are not validated","id":"CVE-2021-39236","kev_date_added":null,"published":"2021-11-19"},{"cvss_score":8.1,"headline":"Apache Ozone: Improper authentication when generating S3 secrets","id":"CVE-2024-45106","kev_date_added":null,"published":"2024-12-03"},{"cvss_score":7.5,"headline":"Ozone S3 Gateway allows bucket and key access to non authenticated users","id":"CVE-2020-17517","kev_date_added":null,"published":"2021-04-27"}],"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 Software Foundation"]},"summary":"Authenticated users can retain access to data via persisted block tokens even after permissions are revoked in Apache Ozone.","url":"https://insights.sbomify.com/CVE-2021-36372/"}