{"answers":{"affected":"2 open source packages ship an affected version, including com.unboundid:unboundid-ldapsdk. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1000134 in the wild and no public exploit code.","fix":"Upgrade com.unboundid:unboundid-ldapsdk to 4.0.5 or later.","what":"CVE-2018-1000134 is a critical authentication bypass vulnerability in n/a, published on 16 Mar 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-1000134 and fix it if it is affected.\n\nWhat it is: CVE-2018-1000134 is a critical authentication bypass vulnerability in n/a, published on 16 Mar 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-1000134 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.unboundid:unboundid-ldapsdk (Maven): affected from 1.1.0; fixed in 4.0.5\n- com.unboundid:unboundid-ldapsdk (Maven): affected from 1.1.0; fixed in 4.0.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-1000134/ (Markdown: https://insights.sbomify.com/CVE-2018-1000134/index.md)","id":"CVE-2018-1000134","markdown":"https://insights.sbomify.com/CVE-2018-1000134/index.md","name":"CVE-2018-1000134","record":{"aliases":["GHSA-qwq9-8rpf-8mp7","RHSA-2018:1713"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"LDAP SDK","requires_auth":"none","summary":"Attackers can impersonate valid users by providing an empty password in synchronous mode due to missing validation in the LDAP SDK.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ldapsdk","vendor":"pingidentity"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-521","name":"Weak Password Requirements"}],"description":"UnboundID LDAP SDK version from commit 801111d8b5c732266a5dbd4b3bb0b6c7b94d7afb up to commit 8471904a02438c03965d21367890276bc25fa5a6, where the issue was reported and fixed contains an Incorrect Access Control vulnerability in process function in SimpleBindRequest class doesn't check for empty password when running in synchronous mode. commit with applied fix https://github.com/pingidentity/ldapsdk/commit/8471904a02438c03965d21367890276bc25fa5a6#diff-f6cb23b459be1ec17df1da33760087fd that can result in Ability to impersonate any valid user. This attack appear to be exploitable via Providing valid username and empty password against servers that do not do additional validation as per https://tools.ietf.org/html/rfc4513#section-5.1.1. This vulnerability appears to have been fixed in after commit 8471904a02438c03965d21367890276bc25fa5a6.","ecosystems":["Maven","Red Hat:rhev_manager:4"],"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":"Weak Password Requirements in UnboundID LDAP SDK","id":"CVE-2018-1000134","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"auth_bypass","year":"2018"},"n_packages":4,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2018-1000135"},"packages":[{"ecosystem":"Maven","fixed":["4.0.5"],"introduced":["1.1.0"],"last_affected":[],"package":"com.unboundid:unboundid-ldapsdk","purl":null,"source":"GHSA-qwq9-8rpf-8mp7"},{"ecosystem":"Maven","fixed":["4.0.5"],"introduced":["1.1.0"],"last_affected":[],"package":"com.unboundid:unboundid-ldapsdk","purl":"pkg:maven/com.unboundid/unboundid-ldapsdk","source":"GHSA-qwq9-8rpf-8mp7"},{"ecosystem":"Red Hat:rhev_manager:4","fixed":["0:4.0.5-1.el7ev"],"introduced":["0"],"last_affected":[],"package":"unboundid-ldapsdk","purl":"pkg:rpm/redhat/unboundid-ldapsdk","source":"RHSA-2018:1713"},{"ecosystem":"Red Hat:rhev_manager:4","fixed":["0:4.0.5-1.el7ev"],"introduced":["0"],"last_affected":[],"package":"unboundid-ldapsdk-javadoc","purl":"pkg:rpm/redhat/unboundid-ldapsdk-javadoc","source":"RHSA-2018:1713"}],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2018-1000133"},"products":["n/a"],"published":"2018-03-16","related":[],"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":"CC BY 4.0","name":"Red Hat","prefix":"RHSA"},{"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 impersonate valid users by providing an empty password in synchronous mode due to missing validation in the LDAP SDK.","url":"https://insights.sbomify.com/CVE-2018-1000134/"}