{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-18352 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-18352 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-18352 is a high-severity missing authorization vulnerability in n/a, published on 18 Feb 2020. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-18352 and fix it if it is affected.\n\nWhat it is: CVE-2019-18352 is a high-severity missing authorization vulnerability in n/a, published on 18 Feb 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-18352 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-18352/ (Markdown: https://insights.sbomify.com/CVE-2019-18352/index.md)","id":"CVE-2019-18352","markdown":"https://insights.sbomify.com/CVE-2019-18352/index.md","name":"CVE-2019-18352","record":{"aliases":["GHSA-ff6j-m9jm-v653"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Industrial network switch","requires_auth":"none","summary":"Improper access control in MAC-based port security allows bypassing restrictions on PHOENIX CONTACT FL NAT devices.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fl_nat_2208_firmware","vendor":"phoenixcontact"},{"product":"fl_nat_2304-2gc-2sfp_firmware","vendor":"phoenixcontact"}],"cvss":{"score":8.2,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:L","version":"3.1"},"cwes":[],"description":"Improper access control exists on PHOENIX CONTACT FL NAT 2208 devices before V2.90 and FL NAT 2304-2GC-2SFP devices before V2.90 when using MAC-based port security.","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":"Missing authorization in n/a","id":"CVE-2019-18352","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Server-side request forgery in n/a","id":"CVE-2019-18355"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-18350"},"products":["n/a"],"published":"2020-02-18","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Improper access control in MAC-based port security allows bypassing restrictions on PHOENIX CONTACT FL NAT devices.","url":"https://insights.sbomify.com/CVE-2019-18352/"}