{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-24072 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-24072 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-24072 is a medium-severity code injection vulnerability in NAVER Whale browser, published on 17 Mar 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-24072 and fix it if it is affected.\n\nWhat it is: CVE-2022-24072 is a medium-severity code injection vulnerability in NAVER Whale browser, published on 17 Mar 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-24072 in the wild and no public exploit code.\n\nAffected product: NAVER Whale browser. 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-24072/ (Markdown: https://insights.sbomify.com/CVE-2022-24072/index.md)","id":"CVE-2022-24072","markdown":"https://insights.sbomify.com/CVE-2022-24072/index.md","name":"CVE-2022-24072","record":{"aliases":["GHSA-j72f-vfwh-m8f9"],"analysis":{"component_type":"browser","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"NAVER Whale browser","requires_auth":"none","summary":"Extension developers can inject arbitrary JavaScript into the extension store page via the devtools API, potentially leading to unauthorized downloads and uploads.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"naver","cpe":[{"product":"whale","vendor":"navercorp"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"The devtools API in Whale browser before 3.12.129.18 allowed extension developers to inject arbitrary JavaScript into the extension store web page via devtools.inspectedWindow, leading to extensions downloading and uploading when users open the developer tool.","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":"Code injection in NAVER Whale browser","id":"CVE-2022-24072","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Open redirect in NAVER Whale browser","id":"CVE-2022-24073"},"packages":[],"prev":{"headline":"Other in NAVER Whale browser","id":"CVE-2022-24071"},"products":["NAVER Whale browser"],"published":"2022-03-17","related":[{"cvss_score":9.8,"headline":"Security feature bypass in NAVER Whale browser","id":"CVE-2025-62583","kev_date_added":null,"published":"2025-10-16"},{"cvss_score":9.8,"headline":"Cross-site scripting in NAVER Whale browser","id":"CVE-2025-53599","kev_date_added":null,"published":"2025-07-04"},{"cvss_score":9.8,"headline":"Missing authorization in NAVER Whale browser","id":"CVE-2022-24074","kev_date_added":null,"published":"2022-03-17"},{"cvss_score":9.1,"headline":"Security feature bypass in NAVER Whale browser","id":"CVE-2025-69234","kev_date_added":null,"published":"2025-12-30"},{"cvss_score":8.1,"headline":"Privilege escalation in n/a","id":"CVE-2018-9859","kev_date_added":null,"published":"2018-06-15"},{"cvss_score":7.8,"headline":"Other in Whale Browser Installer","id":"CVE-2018-12449","kev_date_added":null,"published":"2018-10-11"},{"cvss_score":7.8,"headline":"Other in n/a","id":"CVE-2017-15913","kev_date_added":null,"published":"2018-01-08"}],"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":["NAVER"]},"summary":"Extension developers can inject arbitrary JavaScript into the extension store page via the devtools API, potentially leading to unauthorized downloads and uploads.","url":"https://insights.sbomify.com/CVE-2022-24072/"}