{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2018-6185 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-6185 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-6185 is a medium-severity missing authorization vulnerability in n/a, published on 7 Jun 2019. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-6185 and fix it if it is affected.\n\nWhat it is: CVE-2018-6185 is a medium-severity missing authorization vulnerability in n/a, published on 7 Jun 2019. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-6185 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2018-6185/ (Markdown: https://insights.sbomify.com/CVE-2018-6185/index.md)","id":"CVE-2018-6185","markdown":"https://insights.sbomify.com/CVE-2018-6185/index.md","name":"CVE-2018-6185","record":{"aliases":["GHSA-5c76-8684-p245"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Key Trustee KMS","requires_auth":"high_privilege","summary":"Remote attackers can purge or undelete encryption keys due to insecure default ACLs, causing data loss or recovery of deleted keys.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cloudera_manager","vendor":"cloudera"},{"product":"navigator_key_trustee_kms","vendor":"cloudera"}],"cvss":{"score":4.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-310","name":null}],"description":"In Cloudera Navigator Key Trustee KMS 5.12 and 5.13, incorrect default ACL values allow remote access to purge and undelete API calls on encryption zone keys. The Navigator Key Trustee KMS includes 2 API calls in addition to those in Apache Hadoop KMS: purge and undelete. The KMS ACL values for these commands are keytrustee.kms.acl.PURGE and keytrustee.kms.acl.UNDELETE respectively. The default value for the ACLs in Key Trustee KMS 5.12.0 and 5.13.0 is \"*\" which allows anyone with knowledge of the name of an encryption zone key and network access to the Key Trustee KMS to make those calls against known encryption zone keys. This can result in the recovery of a previously deleted, but not purged, key (undelete) or the deletion of a key in active use (purge) resulting in loss of access to encrypted HDFS data.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Missing authorization in n/a","id":"CVE-2018-6185","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Server-side request forgery in n/a","id":"CVE-2018-6186"},"packages":[],"prev":{"headline":"Directory traversal vulnerability in Next.js","id":"CVE-2018-6184"},"products":["n/a"],"published":"2019-06-07","related":[{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2021-30132","kev_date_added":null,"published":"2021-11-08"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-7399","kev_date_added":null,"published":"2019-11-26"},{"cvss_score":8.1,"headline":"Missing authorization in n/a","id":"CVE-2018-11744","kev_date_added":null,"published":"2019-07-11"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2015-6495","kev_date_added":null,"published":"2019-11-26"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2017-9326","kev_date_added":null,"published":"2019-07-03"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2016-3192","kev_date_added":null,"published":"2019-11-26"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2017-9327","kev_date_added":null,"published":"2019-07-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-05","vendors":["n/a"]},"summary":"Remote attackers can purge or undelete encryption keys due to insecure default ACLs, causing data loss or recovery of deleted keys.","url":"https://insights.sbomify.com/CVE-2018-6185/"}