{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-18379 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-18379 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-18379 is a high-severity server-side request forgery vulnerability in Symantec Messaging Gateway, published on 11 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-18379 and fix it if it is affected.\n\nWhat it is: CVE-2019-18379 is a high-severity server-side request forgery vulnerability in Symantec Messaging Gateway, published on 11 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-18379 in the wild and no public exploit code.\n\nAffected product: Symantec Messaging Gateway. 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-18379/ (Markdown: https://insights.sbomify.com/CVE-2019-18379/index.md)","id":"CVE-2019-18379","markdown":"https://insights.sbomify.com/CVE-2019-18379/index.md","name":"CVE-2019-18379","record":{"aliases":["GHSA-593f-7j6m-g5gq"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Symantec Messaging Gateway","requires_auth":"none","summary":"Attackers can exploit SSRF in Symantec Messaging Gateway to send crafted requests from the backend or access loopback services.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"symantec","cpe":[{"product":"messaging_gateway","vendor":"symantec"}],"cvss":{"score":7.3,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Symantec Messaging Gateway, prior to 10.7.3, may be susceptible to a server-side request forgery (SSRF) exploit, which is a type of issue that can let an attacker send crafted requests from the backend server of a vulnerable web application or access services available through the loopback interface.","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":"Server-side request forgery in Symantec Messaging Gateway","id":"CVE-2019-18379","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in Industrial Control System Protection (ICSP)","id":"CVE-2019-18380"},"packages":[],"prev":{"headline":"Cross-site scripting in Symantec Messaging Gateway","id":"CVE-2019-18378"},"products":["Symantec Messaging Gateway"],"published":"2019-12-11","related":[{"cvss_score":10,"headline":"Code injection in Messaging Gateway","id":"CVE-2017-6326","kev_date_added":null,"published":"2017-06-26"},{"cvss_score":9.8,"headline":"Auth bypass in Symantec Messaging Gateway","id":"CVE-2018-12242","kev_date_added":null,"published":"2018-09-19"},{"cvss_score":8.8,"headline":"XML external entity in Symantec Messaging Gateway","id":"CVE-2018-12243","kev_date_added":null,"published":"2018-09-19"},{"cvss_score":8.2,"headline":"Command injection in n/a","id":"CVE-2016-2204","kev_date_added":null,"published":"2016-04-22"},{"cvss_score":7.9,"headline":"Hardcoded credentials in n/a","id":"CVE-2012-3579","kev_date_added":null,"published":"2012-08-29"},{"cvss_score":7.8,"headline":"Information disclosure in n/a","id":"CVE-2016-2203","kev_date_added":null,"published":"2016-04-22"},{"cvss_score":7.7,"headline":"Missing authorization in n/a","id":"CVE-2012-3580","kev_date_added":null,"published":"2012-08-29"}],"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 exploit SSRF in Symantec Messaging Gateway to send crafted requests from the backend or access loopback services.","url":"https://insights.sbomify.com/CVE-2019-18379/"}