{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-23709 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-23709 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-23709 is a medium-severity missing authorization vulnerability in Elastic Kibana, published on 3 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-23709 and fix it if it is affected.\n\nWhat it is: CVE-2022-23709 is a medium-severity missing authorization vulnerability in Elastic Kibana, published on 3 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-23709 in the wild and no public exploit code.\n\nAffected product: Elastic Kibana. 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-2022-23709/ (Markdown: https://insights.sbomify.com/CVE-2022-23709/index.md)","id":"CVE-2022-23709","markdown":"https://insights.sbomify.com/CVE-2022-23709/index.md","name":"CVE-2022-23709","record":{"aliases":["GHSA-6mp6-6x9r-hvp3"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Kibana monitoring tool","requires_auth":"low_privilege","summary":"Users with Read access to Uptime can modify or disable alerting rules, bypassing intended authorization restrictions in Kibana.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"kibana","vendor":"elastic"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-264","name":null}],"description":"A flaw was discovered in Kibana in which users with Read access to the Uptime feature could modify alerting rules. A user with this privilege would be able to create new alerting rules or overwrite existing ones. However, any new or modified rules would not be enabled, and a user with this privilege could not modify alerting connectors. This effectively means that Read users could disable existing alerting rules.","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":"Missing authorization in kibana","id":"CVE-2022-23709","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"elastic:kibana","products":["elastic:kibana"],"type":"missing_authorization","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in kibana","id":"CVE-2022-23710"},"packages":[],"prev":{"headline":"Elasticsearch privilege escalation","id":"CVE-2022-23708"},"products":["kibana"],"published":"2022-03-03","related":[{"cvss_score":9.8,"headline":"Kibana Arbitrary Code Execution","id":"CVE-2019-7609","kev_date_added":"2022-01-10","published":"2019-03-25"},{"cvss_score":9.9,"headline":"Kibana arbitrary code execution via prototype pollution","id":"CVE-2025-25015","kev_date_added":null,"published":"2025-03-05"},{"cvss_score":9.9,"headline":"Deserialization in Kibana","id":"CVE-2024-37288","kev_date_added":null,"published":"2024-09-09"},{"cvss_score":9.9,"headline":"Code injection in Kibana","id":"CVE-2023-31415","kev_date_added":null,"published":"2023-05-04"},{"cvss_score":9.8,"headline":"Information disclosure in Kibana","id":"CVE-2018-17245","kev_date_added":null,"published":"2018-12-20"},{"cvss_score":9.8,"headline":"Code injection in Kibana","id":"CVE-2018-17246","kev_date_added":null,"published":"2018-12-20"},{"cvss_score":9.1,"headline":"Kibana arbitrary code execution via prototype pollution","id":"CVE-2025-25014","kev_date_added":null,"published":"2025-05-06"}],"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-03","vendors":["Elastic"]},"summary":"Users with Read access to Uptime can modify or disable alerting rules, bypassing intended authorization restrictions in Kibana.","url":"https://insights.sbomify.com/CVE-2022-23709/"}