{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-41906 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-41906 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-41906 is a high-severity server-side request forgery vulnerability in opensearch-project notifications, published on 11 Nov 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-41906 and fix it if it is affected.\n\nWhat it is: CVE-2022-41906 is a high-severity server-side request forgery vulnerability in opensearch-project notifications, published on 11 Nov 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-41906 in the wild and no public exploit code.\n\nAffected product: opensearch-project notifications. 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-41906/ (Markdown: https://insights.sbomify.com/CVE-2022-41906/index.md)","id":"CVE-2022-41906","markdown":"https://insights.sbomify.com/CVE-2022-41906/index.md","name":"CVE-2022-41906","record":{"aliases":["GHSA-pfc4-3436-jgrw"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenSearch notifications plugin","requires_auth":"low_privilege","summary":"Privileged users can exploit SSRF in the OpenSearch Notifications plugin to enumerate services or interact with internal resources via HTTP requests.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"opensearch_notifications","vendor":"amazon"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"OpenSearch Notifications is a notifications plugin for OpenSearch that enables other plugins to send notifications via Email, Slack, Amazon Chime, Custom web-hook etc channels. A potential SSRF issue in OpenSearch Notifications Plugin starting in 2.0.0 and prior to 2.2.1 could allow an existing privileged user to enumerate listening services or interact with configured resources via HTTP requests exceeding the Notification plugin's intended scope. OpenSearch 2.2.1+ contains the fix for this issue. There are currently no recommended workarounds.","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":"OpenSearch Notifications is vulnerable to Server-Side Request Forgery (SSRF)","id":"CVE-2022-41906","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Overflow in `ResizeNearestNeighborGrad` in Tensorflow","id":"CVE-2022-41907"},"packages":[],"prev":{"headline":"wsgidav is vulnerable to Cross-Site Scripting (XSS) when directory browsing is enabled","id":"CVE-2022-41905"},"products":["notifications"],"published":"2022-11-11","related":[],"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":"total"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["opensearch-project"]},"summary":"Privileged users can exploit SSRF in the OpenSearch Notifications plugin to enumerate services or interact with internal resources via HTTP requests.","url":"https://insights.sbomify.com/CVE-2022-41906/"}