{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-19015 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-19015 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-19015 is a critical missing authorization 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-19015 and fix it if it is affected.\n\nWhat it is: CVE-2019-19015 is a critical missing authorization 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-19015 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-19015/ (Markdown: https://insights.sbomify.com/CVE-2019-19015/index.md)","id":"CVE-2019-19015","markdown":"https://insights.sbomify.com/CVE-2019-19015/index.md","name":"CVE-2019-19015","record":{"aliases":["GHSA-g4mq-7pr6-2qjh"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"WebTitan proxy appliance","requires_auth":"none","summary":"Attackers can access the internal PostgreSQL database without authentication via the proxy service, leading to full database control and potential code execution.","user_interaction":"not_required","vuln_class":"missing_authorization"},"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-668","name":"Exposure of Resource to Wrong Sphere"}],"description":"An issue was discovered in TitanHQ WebTitan before 5.18. The proxy service (which is typically exposed to all users) allows connections to the internal PostgreSQL database of the appliance. By connecting to the database through the proxy (without password authentication), an attacker is able to fully control the appliance database. Through this, several different paths exist to gain further access, or execute code.","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-19015","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"SQL injection in n/a","id":"CVE-2019-19016"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2019-19014"},"products":["n/a"],"published":"2019-12-02","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2019-19021","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 access the internal PostgreSQL database without authentication via the proxy service, leading to full database control and potential code execution.","url":"https://insights.sbomify.com/CVE-2019-19015/"}