{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16153 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16153 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16153 is a critical vulnerability in Fortinet FortiSIEM, published on 23 Jan 2020. 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-16153 and fix it if it is affected.\n\nWhat it is: CVE-2019-16153 is a critical vulnerability in Fortinet FortiSIEM, published on 23 Jan 2020. 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-16153 in the wild and no public exploit code.\n\nAffected product: Fortinet FortiSIEM. 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-16153/ (Markdown: https://insights.sbomify.com/CVE-2019-16153/index.md)","id":"CVE-2019-16153","markdown":"https://insights.sbomify.com/CVE-2019-16153/index.md","name":"CVE-2019-16153","record":{"aliases":["GHSA-m9wr-4mrf-cqjr"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Fortinet FortiSIEM","requires_auth":"none","summary":"Attackers can access the FortiSIEM database using static credentials, leading to unauthorized data access and security bypass.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortisiem","vendor":"fortinet"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","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-798","name":"Use of Hard-coded Credentials"}],"description":"A hard-coded password vulnerability in the Fortinet FortiSIEM database component version 5.2.5 and below may allow attackers to access the device database via the use of static credentials.","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":"Hardcoded credentials in Fortinet FortiSIEM","id":"CVE-2019-16153","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in FortiAuthenticator WEB UI","id":"CVE-2019-16154"},"packages":[],"prev":{"headline":"Denial of service in Fortinet FortiClientLinux","id":"CVE-2019-16152"},"products":["Fortinet FortiSIEM"],"published":"2020-01-23","related":[{"cvss_score":9.8,"headline":"Command injection in FortiSIEM","id":"CVE-2025-25256","kev_date_added":null,"published":"2025-08-12"},{"cvss_score":9.7,"headline":"Path traversal in FortiSIEM","id":"CVE-2023-40714","kev_date_added":null,"published":"2025-04-02"},{"cvss_score":9.7,"headline":"Command injection in FortiSIEM","id":"CVE-2024-23108","kev_date_added":null,"published":"2024-02-05"},{"cvss_score":9.7,"headline":"Command injection in FortiSIEM","id":"CVE-2024-23109","kev_date_added":null,"published":"2024-02-05"},{"cvss_score":9.7,"headline":"Command injection in FortiSIEM","id":"CVE-2023-34992","kev_date_added":null,"published":"2023-10-10"},{"cvss_score":9.4,"headline":"Command injection in FortiSIEM","id":"CVE-2025-64155","kev_date_added":null,"published":"2026-01-13"}],"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":"2024-10-25","vendors":["Fortinet"]},"summary":"Attackers can access the FortiSIEM database using static credentials, leading to unauthorized data access and security bypass.","url":"https://insights.sbomify.com/CVE-2019-16153/"}