{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-14023 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-14023 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-14023 is a medium-severity server-side request forgery vulnerability in n/a, published on 22 Sep 2020. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-14023 and fix it if it is affected.\n\nWhat it is: CVE-2020-14023 is a medium-severity server-side request forgery vulnerability in n/a, published on 22 Sep 2020. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-14023 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-2020-14023/ (Markdown: https://insights.sbomify.com/CVE-2020-14023/index.md)","id":"CVE-2020-14023","markdown":"https://insights.sbomify.com/CVE-2020-14023/index.md","name":"CVE-2020-14023","record":{"aliases":["GHSA-9fc4-hf3h-f527"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SMS Gateway","requires_auth":"high_privilege","summary":"Attackers can exploit Server-Side Request Forgery in Ozeki NG SMS Gateway to access internal resources via SMS WCF or RSS features.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ozeki_ng_sms_gateway","vendor":"ozeki"}],"cvss":{"score":4.9,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Ozeki NG SMS Gateway through 4.17.6 allows SSRF via SMS WCF or RSS To SMS.","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 n/a","id":"CVE-2020-14023","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-14024"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2020-14022"},"products":["n/a"],"published":"2020-09-22","related":[{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2020-14022","kev_date_added":null,"published":"2020-09-22"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2020-14025","kev_date_added":null,"published":"2020-09-22"},{"cvss_score":8.8,"headline":"Other in n/a","id":"CVE-2020-14026","kev_date_added":null,"published":"2020-09-22"},{"cvss_score":7.5,"headline":"XML external entity in n/a","id":"CVE-2020-14029","kev_date_added":null,"published":"2020-09-18"},{"cvss_score":7.2,"headline":"Deserialization in n/a","id":"CVE-2020-14030","kev_date_added":null,"published":"2020-09-29"},{"cvss_score":7.2,"headline":"Path traversal in n/a","id":"CVE-2020-14028","kev_date_added":null,"published":"2020-09-22"},{"cvss_score":7.2,"headline":"Path traversal in n/a","id":"CVE-2020-14031","kev_date_added":null,"published":"2020-09-22"}],"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-04","vendors":["n/a"]},"summary":"Attackers can exploit Server-Side Request Forgery in Ozeki NG SMS Gateway to access internal resources via SMS WCF or RSS features.","url":"https://insights.sbomify.com/CVE-2020-14023/"}