{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-4669 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-4669 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-4669 is a critical vulnerability in Exagate SYSGuard 3001, published on 14 Sep 2023."},"fix_prompt":"Check this codebase for CVE-2023-4669 and fix it if it is affected.\n\nWhat it is: CVE-2023-4669 is a critical vulnerability in Exagate SYSGuard 3001, published on 14 Sep 2023. \nExploitation: There is no known exploitation of CVE-2023-4669 in the wild and no public exploit code.\n\nAffected product: Exagate SYSGuard 3001. 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-4669/ (Markdown: https://insights.sbomify.com/CVE-2023-4669/index.md)","id":"CVE-2023-4669","markdown":"https://insights.sbomify.com/CVE-2023-4669/index.md","name":"CVE-2023-4669","record":{"aliases":["GHSA-fx87-2qcr-264f"],"analysis":null,"analysis_generated_by":null,"assigner":"TR-CERT","cpe":[{"product":"sysguard_3001_firmware","vendor":"exagate"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"},{"id":"CWE-302","name":"Authentication Bypass by Assumed-Immutable Data"}],"description":"Authentication Bypass by Assumed-Immutable Data vulnerability in Exagate SYSGuard 3001 allows Authentication Bypass.\n\nThis issue affects SYSGuard 3001: before 3.2.20.0.","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":"Authentication Bypass in Exagate SYSGuard 3001","id":"CVE-2023-4669","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"SQLi in Innosa's Probbys","id":"CVE-2023-4670"},"packages":[],"prev":{"headline":"Ad Inserter \u003c= 2.7.30 - Unauthenticated Sensitive Information Exposure via ai-debug-processing-fe","id":"CVE-2023-4668"},"products":["SYSGuard 3001"],"published":"2023-09-14","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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-21","vendors":["Exagate"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2023-4669/"}