{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10127 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-10127 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-10127 is a high-severity vulnerability in Postgresql Postgresql, published on 19 Mar 2021. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-10127 and fix it if it is affected.\n\nWhat it is: CVE-2019-10127 is a high-severity vulnerability in Postgresql Postgresql, published on 19 Mar 2021. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-10127 in the wild and no public exploit code.\n\nAffected product: Postgresql Postgresql. 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-10127/ (Markdown: https://insights.sbomify.com/CVE-2019-10127/index.md)","id":"CVE-2019-10127","markdown":"https://insights.sbomify.com/CVE-2019-10127/index.md","name":"CVE-2019-10127","record":{"aliases":["GHSA-q78v-pr3r-qpf7"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["code_execution","data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PostgreSQL database","requires_auth":"low_privilege","summary":"Insecure default ACLs in the Windows installer allow attackers to execute code, read, or delete database files via the service account.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"postgresql","vendor":"postgresql"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"A vulnerability was found in postgresql versions 11.x prior to 11.3. The Windows installer for BigSQL-supplied PostgreSQL does not lock down the ACL of the binary installation directory or the ACL of the data directory; it keeps the inherited ACL. In the default configuration, an attacker having both an unprivileged Windows account and an unprivileged PostgreSQL account can cause the PostgreSQL service account to execute arbitrary code. An attacker having only the unprivileged Windows account can read arbitrary data directory files, essentially bypassing database-imposed read access limitations. An attacker having only the unprivileged Windows account can also delete certain data directory files.","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":"Misconfiguration in postgresql","id":"CVE-2019-10127","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"postgresql:postgresql","products":["postgresql:postgresql"],"type":"misconfiguration","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Misconfiguration in postgresql","id":"CVE-2019-10128"},"packages":[],"prev":{"headline":"Memory corruption in kernel","id":"CVE-2019-10126"},"products":["postgresql"],"published":"2021-03-19","related":[{"cvss_score":10,"headline":"Information disclosure in n/a","id":"CVE-2013-1902","kev_date_added":null,"published":"2013-04-04"},{"cvss_score":10,"headline":"Information disclosure in n/a","id":"CVE-2013-1903","kev_date_added":null,"published":"2013-04-04"},{"cvss_score":10,"headline":"Privilege escalation in n/a","id":"CVE-2007-3279","kev_date_added":null,"published":"2007-06-19"},{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2002-1399","kev_date_added":null,"published":"2003-01-08"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2016-3065","kev_date_added":null,"published":"2016-04-11"},{"cvss_score":9,"headline":"Code injection in n/a","id":"CVE-2007-3280","kev_date_added":null,"published":"2007-06-19"},{"cvss_score":8.8,"headline":"PostgreSQL tsvector and tsquery undersize allocations, via integer wraparound","id":"CVE-2026-14662","kev_date_added":null,"published":"2026-08-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Insecure default ACLs in the Windows installer allow attackers to execute code, read, or delete database files via the service account.","url":"https://insights.sbomify.com/CVE-2019-10127/"}