{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-19021 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-19021 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-19021 is a critical vulnerability in n/a, published on 2 Dec 2019. 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-19021 and fix it if it is affected.\n\nWhat it is: CVE-2019-19021 is a critical vulnerability in n/a, published on 2 Dec 2019. 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-19021 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-19021/ (Markdown: https://insights.sbomify.com/CVE-2019-19021/index.md)","id":"CVE-2019-19021","markdown":"https://insights.sbomify.com/CVE-2019-19021/index.md","name":"CVE-2019-19021","record":{"aliases":["GHSA-rcmf-fgmg-6243"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WebTitan web filter","requires_auth":"none","summary":"Attackers can gain administrator access to WebTitan via a hidden support account with a hard-coded password, leading to full system compromise.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"webtitan","vendor":"titanhq"}],"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":"An issue was discovered in TitanHQ WebTitan before 5.18. It has a hidden support account (with a hard-coded password) in the web administration interface, with administrator privileges. Anybody can log in with this account.","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 n/a","id":"CVE-2019-19021","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2019-19022"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2019-19020"},"products":["n/a"],"published":"2019-12-02","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2019-19015","kev_date_added":null,"published":"2019-12-02"},{"cvss_score":8.1,"headline":"Hardcoded credentials in n/a","id":"CVE-2019-19017","kev_date_added":null,"published":"2019-12-02"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2019-19014","kev_date_added":null,"published":"2019-12-02"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2019-19016","kev_date_added":null,"published":"2019-12-02"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2019-19019","kev_date_added":null,"published":"2019-12-02"},{"cvss_score":7.2,"headline":"File upload in n/a","id":"CVE-2019-19020","kev_date_added":null,"published":"2019-12-02"}],"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-05","vendors":["n/a"]},"summary":"Attackers can gain administrator access to WebTitan via a hidden support account with a hard-coded password, leading to full system compromise.","url":"https://insights.sbomify.com/CVE-2019-19021/"}