{"answers":{"affected":"2 open source packages ship an affected version, including org.postgresql:pgjdbc-aggregate. It affects 2 products.","exploited":"There is no known exploitation of CVE-2018-10936 in the wild and no public exploit code.","fix":"Upgrade org.postgresql:pgjdbc-aggregate to 42.2.5 or later.","what":"CVE-2018-10936 is a high-severity vulnerability in Redhat Enterprise Linux, published on 30 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-10936 and fix it if it is affected.\n\nWhat it is: CVE-2018-10936 is a high-severity vulnerability in Redhat Enterprise Linux, published on 30 Aug 2018. 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-2018-10936 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.postgresql:pgjdbc-aggregate (Maven): affected all versions; fixed in 42.2.5\n- org.postgresql:pgjdbc-aggregate (Maven): affected all versions; fixed in 42.2.5\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-10936/ (Markdown: https://insights.sbomify.com/CVE-2018-10936/index.md)","id":"CVE-2018-10936","markdown":"https://insights.sbomify.com/CVE-2018-10936/index.md","name":"CVE-2018-10936","record":{"aliases":["DEBIAN-CVE-2018-10936","GHSA-568q-9fw5-28wf","UBUNTU-CVE-2018-10936"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"PostgreSQL JDBC driver","requires_auth":"none","summary":"Man-in-the-middle attackers can masquerade as trusted servers by bypassing hostname verification in the PostgreSQL JDBC driver.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"postgresql_jdbc_driver","vendor":"postgresql"},{"product":"enterprise_linux","vendor":"redhat"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-297","name":"Improper Validation of Certificate with Host Mismatch"}],"description":"A weakness was found in postgresql-jdbc before version 42.2.5. It was possible to provide an SSL Factory and not check the host name if a host name verifier was not provided to the driver. This could lead to a condition where a man-in-the-middle attacker could masquerade as a trusted server by providing a certificate for the wrong host, as long as it was signed by a trusted CA.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2018-11-19","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2018-11-19T13:09:47Z","kind":"github_poc","ref":"https://github.com/tafamace/CVE-2018-10936","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":true,"headline":"Moderate severity vulnerability that affects org.postgresql:pgjdbc-aggregate","id":"CVE-2018-10936","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"redhat:enterprise_linux","products":["redhat:enterprise_linux"],"type":"security_feature_bypass","year":"2018"},"n_packages":2,"n_references":4,"next":{"headline":"Cross-site scripting in Openshift Container Platform","id":"CVE-2018-10937"},"packages":[{"ecosystem":"Maven","fixed":["42.2.5"],"introduced":["0"],"last_affected":[],"package":"org.postgresql:pgjdbc-aggregate","purl":null,"source":"GHSA-568q-9fw5-28wf"},{"ecosystem":"Maven","fixed":["42.2.5"],"introduced":["0"],"last_affected":[],"package":"org.postgresql:pgjdbc-aggregate","purl":"pkg:maven/org.postgresql/pgjdbc-aggregate","source":"GHSA-568q-9fw5-28wf"}],"prev":{"headline":"Denial of service in 389-ds-base","id":"CVE-2018-10935"},"products":["PostgreSQL"],"published":"2018-08-30","related":[{"cvss_score":8.2,"headline":"Silent channel-binding authentication downgrade via unsupported certificate algorithms","id":"CVE-2026-54291","kev_date_added":null,"published":"2026-07-06"},{"cvss_score":8.2,"headline":"pgjdbc Client Allows Fallback to Insecure Authentication Despite channelBinding=require Configuration","id":"CVE-2025-49146","kev_date_added":null,"published":"2025-06-11"},{"cvss_score":7.5,"headline":"pgjdbc: Unbounded PBKDF2 iterations in SCRAM authentication allows CPU exhaustion DoS","id":"CVE-2026-42198","kev_date_added":null,"published":"2026-04-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["[UNKNOWN]"]},"summary":"Man-in-the-middle attackers can masquerade as trusted servers by bypassing hostname verification in the PostgreSQL JDBC driver.","url":"https://insights.sbomify.com/CVE-2018-10936/"}