{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-17517 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-17517 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-17517 is a high-severity missing authorization vulnerability in Apache Ozone, published on 27 Apr 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-2020-17517 and fix it if it is affected.\n\nWhat it is: CVE-2020-17517 is a high-severity missing authorization vulnerability in Apache Ozone, published on 27 Apr 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-2020-17517 in the wild and no public exploit code.\n\nAffected product: Apache Ozone. 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-17517/ (Markdown: https://insights.sbomify.com/CVE-2020-17517/index.md)","id":"CVE-2020-17517","markdown":"https://insights.sbomify.com/CVE-2020-17517/index.md","name":"CVE-2020-17517","record":{"aliases":["GHSA-h253-pq36-ggpj"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Ozone S3 Gateway","requires_auth":"none","summary":"Unauthenticated users can access S3 buckets and keys in Apache Ozone clusters, exposing sensitive data to anonymous clients.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"ozone","vendor":"apache"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"},{"id":"CWE-285","name":"Improper Authorization"}],"description":"The S3 buckets and keys in a secure Apache Ozone Cluster must be inaccessible to anonymous access by default. The current security vulnerability allows access to keys and buckets through a curl command or an unauthenticated HTTP request. This enables unauthorized access to buckets and keys thereby exposing data to anonymous clients or users. This affected Apache Ozone prior to the 1.1.0 release.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Ozone S3 Gateway allows bucket and key access to non authenticated users","id":"CVE-2020-17517","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Apache Flink directory traversal attack: remote file writing through the REST API","id":"CVE-2020-17518"},"packages":[],"prev":{"headline":"Authentication Bypass in Apache Cassandra","id":"CVE-2020-17516"},"products":["Apache Ozone"],"published":"2021-04-27","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"}],"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":["Apache Software Foundation"]},"summary":"Unauthenticated users can access S3 buckets and keys in Apache Ozone clusters, exposing sensitive data to anonymous clients.","url":"https://insights.sbomify.com/CVE-2020-17517/"}