{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.ozone:ozone. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-45106 in the wild and no public exploit code.","fix":"Upgrade org.apache.ozone:ozone to 1.4.1 or later.","what":"CVE-2024-45106 is a high-severity missing authorization vulnerability in Apache Ozone, published on 3 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-45106 and fix it if it is affected.\n\nWhat it is: CVE-2024-45106 is a high-severity missing authorization vulnerability in Apache Ozone, published on 3 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-45106 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.ozone:ozone (Maven): affected from 1.4.0; fixed in 1.4.1\n- org.apache.ozone:ozone (Maven): affected from 1.4.0; fixed in 1.4.1\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-2024-45106/ (Markdown: https://insights.sbomify.com/CVE-2024-45106/index.md)","id":"CVE-2024-45106","markdown":"https://insights.sbomify.com/CVE-2024-45106/index.md","name":"CVE-2024-45106","record":{"aliases":["GHSA-rcq8-9q3j-98mw"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Apache Ozone S3 Gateway","requires_auth":"low_privilege","summary":"Authenticated Kerberos users can revoke and regenerate other users' S3 secrets if specific non-default configurations are enabled.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"ozone","vendor":"apache"}],"cvss":{"score":8.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"Improper authentication of an HTTP endpoint in the S3 Gateway of Apache Ozone 1.4.0 allows any authenticated Kerberos user to revoke and regenerate the S3 secrets of any other user. This is only possible if:\n  *  ozone.s3g.secret.http.enabled is set to true. The default value of this configuration is false.\n  *  The user configured in ozone.s3g.kerberos.principal is also configured in ozone.s3.administrators or ozone.administrators.\n\nUsers are recommended to upgrade to Apache Ozone version 1.4.1 which disables the affected endpoint.","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":"Apache Ozone: Improper authentication when generating S3 secrets","id":"CVE-2024-45106","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":2,"n_references":1,"next":{"headline":"ZDI-CAN-24186: Adobe Acrobat Reader DC Doc Object Use-After-Free Information Disclosure Vulnerability","id":"CVE-2024-45107"},"packages":[{"ecosystem":"Maven","fixed":["1.4.1"],"introduced":["1.4.0"],"last_affected":[],"package":"org.apache.ozone:ozone","purl":null,"source":"GHSA-rcq8-9q3j-98mw"},{"ecosystem":"Maven","fixed":["1.4.1"],"introduced":["1.4.0"],"last_affected":[],"package":"org.apache.ozone:ozone","purl":"pkg:maven/org.apache.ozone/ozone","source":"GHSA-rcq8-9q3j-98mw"}],"prev":{"headline":"Code injection in HX1331 Certified Node (ThinkAgile) BIOS","id":"CVE-2024-45105"},"products":["Apache Ozone"],"published":"2024-12-03","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":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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-12-03","vendors":["Apache Software Foundation"]},"summary":"Authenticated Kerberos users can revoke and regenerate other users' S3 secrets if specific non-default configurations are enabled.","url":"https://insights.sbomify.com/CVE-2024-45106/"}