{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-22151 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-22151 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-22151 is a low-severity path traversal vulnerability in Elastic Kibana, published on 22 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-22151 and fix it if it is affected.\n\nWhat it is: CVE-2021-22151 is a low-severity path traversal vulnerability in Elastic Kibana, published on 22 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-22151 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-2021-22151/ (Markdown: https://insights.sbomify.com/CVE-2021-22151/index.md)","id":"CVE-2021-22151","markdown":"https://insights.sbomify.com/CVE-2021-22151/index.md","name":"CVE-2021-22151","record":{"aliases":["GHSA-rj62-3vmp-2f6j"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Kibana visualization tool","requires_auth":"low_privilege","summary":"A malicious user can traverse the Kibana host to read internal files ending in .pbf due to lack of path validation.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"kibana","vendor":"elastic"}],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"It was discovered that Kibana was not validating a user supplied path, which would load .pbf files. Because of this, a malicious user could arbitrarily traverse the Kibana host to load internal files ending in the .pbf extension.","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":"Kibana path traversal issue","id":"CVE-2021-22151","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"elastic:kibana","products":["elastic:kibana"],"type":"path_traversal","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2021-22152"},"packages":[],"prev":{"headline":"Kibana code execution issue","id":"CVE-2021-22150"},"products":["Kibana"],"published":"2023-11-22","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-11","vendors":["Elastic"]},"summary":"A malicious user can traverse the Kibana host to read internal files ending in .pbf due to lack of path validation.","url":"https://insights.sbomify.com/CVE-2021-22151/"}