{"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-41532 in the wild and no public exploit code.","fix":"Upgrade org.apache.ozone:ozone-main to 1.2.0 or later.","what":"CVE-2021-41532 is a medium-severity missing authorization 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-41532 and fix it if it is affected.\n\nWhat it is: CVE-2021-41532 is a medium-severity missing authorization 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-41532 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-41532/ (Markdown: https://insights.sbomify.com/CVE-2021-41532/index.md)","id":"CVE-2021-41532","markdown":"https://insights.sbomify.com/CVE-2021-41532/index.md","name":"CVE-2021-41532","record":{"aliases":["GHSA-gc37-9g7f-96fx"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Ozone","requires_auth":"none","summary":"Unauthenticated attackers can access sensitive metadata from Apache Ozone Recon HTTP endpoints due to missing authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"ozone","vendor":"apache"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"In Apache Ozone before 1.2.0, Recon HTTP endpoints provide access to OM, SCM and Datanode metadata. Due to a bug, any unauthenticated user can access the data from these endpoints.","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":"Unauthenticated access to Ozone Recon HTTP endpoints","id":"CVE-2021-41532","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"missing_authorization","year":"2021"},"n_packages":2,"n_references":2,"next":{"headline":"Information disclosure in NX 1980 Series","id":"CVE-2021-41533"},"packages":[{"ecosystem":"Maven","fixed":["1.2.0"],"introduced":["0"],"last_affected":[],"package":"org.apache.ozone:ozone-main","purl":null,"source":"GHSA-gc37-9g7f-96fx"},{"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-gc37-9g7f-96fx"}],"prev":{"headline":"Invalid RPKI data could disable Route Origin Validation on RTR clients.","id":"CVE-2021-41531"},"products":["Apache Ozone"],"published":"2021-11-19","related":[{"cvss_score":9.8,"headline":"Original block tokens are persisted and can be retrieved","id":"CVE-2021-36372","kev_date_added":null,"published":"2021-11-19"},{"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":"Unauthenticated attackers can access sensitive metadata from Apache Ozone Recon HTTP endpoints due to missing authorization checks.","url":"https://insights.sbomify.com/CVE-2021-41532/"}