{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-34914 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-34914 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-34914 is a critical command injection vulnerability in n/a, published on 8 Jul 2022. 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-34914 and fix it if it is affected.\n\nWhat it is: CVE-2022-34914 is a critical command injection vulnerability in n/a, published on 8 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-34914 in the wild and no public exploit code.\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-34914/ (Markdown: https://insights.sbomify.com/CVE-2022-34914/index.md)","id":"CVE-2022-34914","markdown":"https://insights.sbomify.com/CVE-2022-34914/index.md","name":"CVE-2022-34914","record":{"aliases":["GHSA-38x3-v328-497c"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Webswing application server","requires_auth":"none","summary":"Attackers can inject arbitrary arguments into session startup via manipulated X-Forwarded-For headers if the clientIp variable is used in configuration.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"webswing","vendor":"webswing"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"Webswing before 22.1.3 allows X-Forwarded-For header injection. The client IP address is associated with a variable in the configuration page. The {clientIp} variable can be used as an application startup argument. The X-Forwarded-For header can be manipulated by a client to store an arbitrary value that is used to replace the clientIp variable (without sanitization). A client can thus inject multiple arguments into the session startup. Systems that do not use the clientIP variable in the configuration are not vulnerable. The vulnerability is fixed in these versions: 20.1.16, 20.2.19, 21.1.8, 21.2.12, and 22.1.3.","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":"Command injection in n/a","id":"CVE-2022-34914","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Improper Input Validation (JNDI Injection) in JMSMessageConsumer","id":"CVE-2022-34916"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2022-34913"},"products":["n/a"],"published":"2022-07-08","related":[{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2024-39332","kev_date_added":null,"published":"2024-10-31"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2020-11103","kev_date_added":null,"published":"2020-12-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can inject arbitrary arguments into session startup via manipulated X-Forwarded-For headers if the clientIp variable is used in configuration.","url":"https://insights.sbomify.com/CVE-2022-34914/"}