{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-5102 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-5102 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-5102 is a medium-severity vulnerability in SICK AG APU0200, published on 9 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-5102 and fix it if it is affected.\n\nWhat it is: CVE-2023-5102 is a medium-severity vulnerability in SICK AG APU0200, published on 9 Oct 2023. 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-2023-5102 in the wild and no public exploit code.\n\nAffected product: SICK AG APU0200. 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-2023-5102/ (Markdown: https://insights.sbomify.com/CVE-2023-5102/index.md)","id":"CVE-2023-5102","markdown":"https://insights.sbomify.com/CVE-2023-5102/index.md","name":"CVE-2023-5102","record":{"aliases":["GHSA-gxxp-j837-wmrj"],"analysis":{"component_type":"ics_ot","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SICK APU","requires_auth":"none","summary":"An unprivileged remote attacker can enable hidden functionality in SICK APU devices via HTTP requests due to insufficient control flow management.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SICK AG","cpe":[{"product":"apu0200_firmware","vendor":"sick"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-691","name":"Insufficient Control Flow Management"}],"description":"Insufficient Control Flow Management in RDT400 in SICK APU allows an unprivileged remote attacker to potentially enable hidden functionality via HTTP requests.","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":"Security feature bypass in APU0200","id":"CVE-2023-5102","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in APU0200","id":"CVE-2023-5103"},"packages":[],"prev":{"headline":"Information disclosure in APU0200","id":"CVE-2023-5101"},"products":["APU0200"],"published":"2023-10-09","related":[{"cvss_score":8.2,"headline":"Missing authorization in APU0200","id":"CVE-2023-43696","kev_date_added":null,"published":"2023-10-09"},{"cvss_score":7.7,"headline":"Missing authorization in APU0200","id":"CVE-2023-43700","kev_date_added":null,"published":"2023-10-09"},{"cvss_score":7.5,"headline":"Auth bypass in APU0200","id":"CVE-2023-43699","kev_date_added":null,"published":"2023-10-09"},{"cvss_score":7.1,"headline":"Cross-site scripting in APU0200","id":"CVE-2023-43698","kev_date_added":null,"published":"2023-10-09"},{"cvss_score":6.5,"headline":"Path traversal in APU0200","id":"CVE-2023-43697","kev_date_added":null,"published":"2023-10-09"},{"cvss_score":5.9,"headline":"Information disclosure in APU0200","id":"CVE-2023-5100","kev_date_added":null,"published":"2023-10-09"},{"cvss_score":5.3,"headline":"Information disclosure in APU0200","id":"CVE-2023-5101","kev_date_added":null,"published":"2023-10-09"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-12-09","vendors":["SICK AG"]},"summary":"An unprivileged remote attacker can enable hidden functionality in SICK APU devices via HTTP requests due to insufficient control flow management.","url":"https://insights.sbomify.com/CVE-2023-5102/"}