{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-11749 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-11749 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-11749 is a critical vulnerability in Puppet Puppet Enterprise, published on 24 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-11749 and fix it if it is affected.\n\nWhat it is: CVE-2018-11749 is a critical vulnerability in Puppet Puppet Enterprise, published on 24 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-11749 in the wild and no public exploit code.\n\nAffected product: Puppet Puppet Enterprise. 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-11749/ (Markdown: https://insights.sbomify.com/CVE-2018-11749/index.md)","id":"CVE-2018-11749","markdown":"https://insights.sbomify.com/CVE-2018-11749/index.md","name":"CVE-2018-11749","record":{"aliases":["GHSA-qh8x-vwrj-w4f2"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Puppet Enterprise","requires_auth":"none","summary":"Puppet Enterprise sends user credentials in plaintext when startTLS with RBAC LDAP is configured, allowing attackers to intercept sensitive login information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"puppet","cpe":[{"product":"puppet_enterprise","vendor":"puppet"}],"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-319","name":"Cleartext Transmission of Sensitive Information"}],"description":"When users are configured to use startTLS with RBAC LDAP, at login time, the user's credentials are sent via plaintext to the LDAP server. This affects Puppet Enterprise 2018.1.3, 2017.3.9, and 2016.4.14, and is fixed in Puppet Enterprise 2018.1.4, 2017.3.10, and 2016.4.15. It scored an 8.5 CVSS score.","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":"Information disclosure in Puppet Enterprise","id":"CVE-2018-11749","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"puppet:puppet_enterprise","products":["puppet:puppet_enterprise"],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2018-11750"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-11748"},"products":["Puppet Enterprise"],"published":"2018-08-24","related":[{"cvss_score":9.8,"headline":"Privilege escalation in Puppet Enterprise","id":"CVE-2023-2530","kev_date_added":null,"published":"2023-06-07"},{"cvss_score":9.8,"headline":"Hardcoded credentials in Puppet Enterprise","id":"CVE-2019-10694","kev_date_added":null,"published":"2019-12-11"},{"cvss_score":8.8,"headline":"Other in Puppet Enterprise","id":"CVE-2021-27020","kev_date_added":null,"published":"2021-08-30"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2015-5686","kev_date_added":null,"published":"2020-02-27"},{"cvss_score":8.8,"headline":"Code injection in Puppet Enterprise","id":"CVE-2016-5716","kev_date_added":null,"published":"2017-08-09"},{"cvss_score":8.8,"headline":"Security feature bypass in n/a","id":"CVE-2015-7330","kev_date_added":null,"published":"2016-04-11"}],"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":["Puppet"]},"summary":"Puppet Enterprise sends user credentials in plaintext when startTLS with RBAC LDAP is configured, allowing attackers to intercept sensitive login information.","url":"https://insights.sbomify.com/CVE-2018-11749/"}