{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-17123 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-17123 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-17123 is a high-severity vulnerability in n/a, published on 13 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-17123 and fix it if it is affected.\n\nWhat it is: CVE-2019-17123 is a high-severity vulnerability in n/a, published on 13 Dec 2019. 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-2019-17123 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-2019-17123/ (Markdown: https://insights.sbomify.com/CVE-2019-17123/index.md)","id":"CVE-2019-17123","markdown":"https://insights.sbomify.com/CVE-2019-17123/index.md","name":"CVE-2019-17123","record":{"aliases":["GHSA-pmmq-6pp3-rf2g"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"eGain Web Email API","requires_auth":"none","summary":"Attackers can spoof email messages via header injection in the eGain Web Email API, potentially misleading recipients about the sender's identity.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mail","vendor":"egain"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"The eGain Web Email API 11+ allows spoofed messages because the fromName and message fields (to /system/ws/v11/ss/email) are mishandled, as demonstrated by fromName header injection with a %0a or %0d character. (Also, the message parameter can have initial HTML comment characters.)","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":"Other in n/a","id":"CVE-2019-17123","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2019-17124"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-17121"},"products":["n/a"],"published":"2019-12-13","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can spoof email messages via header injection in the eGain Web Email API, potentially misleading recipients about the sender's identity.","url":"https://insights.sbomify.com/CVE-2019-17123/"}