{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1052 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2018-1052 is a medium-severity vulnerability in Postgresql Postgresql, published on 9 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-1052 and fix it if it is affected.\n\nWhat it is: CVE-2018-1052 is a medium-severity vulnerability in Postgresql Postgresql, published on 9 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-1052 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-2018-1052/ (Markdown: https://insights.sbomify.com/CVE-2018-1052/index.md)","id":"CVE-2018-1052","markdown":"https://insights.sbomify.com/CVE-2018-1052/index.md","name":"CVE-2018-1052","record":{"aliases":["ALPINE-CVE-2018-1052","CLEANSTART-2026-SZ74267","GHSA-qwcr-cgjv-9rp7"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"PostgreSQL database","requires_auth":"low_privilege","summary":"An authenticated attacker can read arbitrary server memory bytes by inserting crafted data into a partitioned table in PostgreSQL.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"postgresql","vendor":"postgresql"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Memory disclosure vulnerability in table partitioning was found in postgresql 10.x before 10.2, allowing an authenticated attacker to read arbitrary bytes of server memory via purpose-crafted insert to a partitioned table.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information disclosure in postgresql","id":"CVE-2018-1052","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"postgresql:postgresql","products":["postgresql:postgresql"],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in postgresql","id":"CVE-2018-1053"},"packages":[],"prev":{"headline":"Deserialization of Untrusted Data in org.jboss.resteasy:resteasy-yaml-provider","id":"CVE-2018-1051"},"products":["postgresql"],"published":"2018-02-09","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-09-16","vendors":["The PostgreSQL Global Development Group"]},"summary":"An authenticated attacker can read arbitrary server memory bytes by inserting crafted data into a partitioned table in PostgreSQL.","url":"https://insights.sbomify.com/CVE-2018-1052/"}