{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-7059 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-7059 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-7059 is a high-severity vulnerability in n/a, published on 6 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-7059 and fix it if it is affected.\n\nWhat it is: CVE-2018-7059 is a high-severity vulnerability in n/a, published on 6 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-7059 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-7059/ (Markdown: https://insights.sbomify.com/CVE-2018-7059/index.md)","id":"CVE-2018-7059","markdown":"https://insights.sbomify.com/CVE-2018-7059/index.md","name":"CVE-2018-7059","record":{"aliases":["GHSA-44c7-h9h2-wj6v"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Aruba ClearPass","requires_auth":"low_privilege","summary":"An authenticated user with monitoring permissions can exploit an API flaw to obtain cluster credentials, leading to privilege escalation.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hpe","cpe":[{"product":"aruba_clearpass_policy_manager","vendor":"hp"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Aruba ClearPass prior to 6.6.9 has a vulnerability in the API that helps to coordinate cluster actions. An authenticated user with the \"mon\" permission could use this vulnerability to obtain cluster credentials which could allow privilege escalation. This vulnerability is only present when authenticated as a user with \"mon\" permission.","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":"Information disclosure in n/a","id":"CVE-2018-7059","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site request forgery in Aruba ClearPass","id":"CVE-2018-7060"},"packages":[],"prev":{"headline":"Auth bypass in Aruba ClearPass","id":"CVE-2018-7058"},"products":["n/a"],"published":"2018-08-06","related":[{"cvss_score":9.8,"headline":"Auth bypass in Aruba ClearPass","id":"CVE-2018-7058","kev_date_added":null,"published":"2018-08-06"},{"cvss_score":9.8,"headline":"Code injection in Aruba ClearPass Policy Manager","id":"CVE-2017-5824","kev_date_added":null,"published":"2018-02-15"},{"cvss_score":8.8,"headline":"Privilege escalation in Aruba ClearPass Policy Manager","id":"CVE-2017-5825","kev_date_added":null,"published":"2018-02-15"},{"cvss_score":8.8,"headline":"Code injection in Aruba ClearPass Policy Manager","id":"CVE-2017-5826","kev_date_added":null,"published":"2018-02-15"},{"cvss_score":8.1,"headline":"Command injection in Aruba ClearPass","id":"CVE-2017-9001","kev_date_added":null,"published":"2018-08-06"},{"cvss_score":8.1,"headline":"XML external entity in Aruba ClearPass Policy Manager","id":"CVE-2017-5828","kev_date_added":null,"published":"2018-02-15"}],"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":"An authenticated user with monitoring permissions can exploit an API flaw to obtain cluster credentials, leading to privilege escalation.","url":"https://insights.sbomify.com/CVE-2018-7059/"}