{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45027 exists.","fix":"No fix has been published for CVE-2022-45027 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-45027 is a medium-severity server-side request forgery vulnerability in n/a, published on 1 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-45027 and fix it if it is affected.\n\nWhat it is: CVE-2022-45027 is a medium-severity server-side request forgery vulnerability in n/a, published on 1 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45027 exists.\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-2022-45027/ (Markdown: https://insights.sbomify.com/CVE-2022-45027/index.md)","id":"CVE-2022-45027","markdown":"https://insights.sbomify.com/CVE-2022-45027/index.md","name":"CVE-2022-45027","record":{"aliases":["GHSA-g9r7-hq6j-vv4r"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"perfSONAR monitoring tool","requires_auth":"none","summary":"Attackers can exploit improper header handling in participant discovery to perform Server-Side Request Forgery, potentially accessing internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"perfsonar","vendor":"perfsonar"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"perfSONAR before 4.4.6, when performing participant discovery, incorrectly uses an HTTP request header value to determine a local address.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Server-side request forgery in n/a","id":"CVE-2022-45027","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2022-45028"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2022-45026"},"products":["n/a"],"published":"2023-01-01","related":[{"cvss_score":8.6,"headline":"Server-side request forgery in n/a","id":"CVE-2022-41412","kev_date_added":null,"published":"2022-11-30"},{"cvss_score":5.3,"headline":"Path traversal in n/a","id":"CVE-2022-45213","kev_date_added":null,"published":"2023-01-01"},{"cvss_score":4.3,"headline":"Cross-site request forgery in n/a","id":"CVE-2022-41413","kev_date_added":null,"published":"2022-11-30"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-11","vendors":["n/a"]},"summary":"Attackers can exploit improper header handling in participant discovery to perform Server-Side Request Forgery, potentially accessing internal resources.","url":"https://insights.sbomify.com/CVE-2022-45027/"}