{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2002-0374 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2002-0374 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-0374 is a high-severity vulnerability in n/a, published on 2 Apr 2003."},"fix_prompt":"Check this codebase for CVE-2002-0374 and fix it if it is affected.\n\nWhat it is: CVE-2002-0374 is a high-severity vulnerability in n/a, published on 2 Apr 2003. \nExploitation: There is no known exploitation of CVE-2002-0374 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2002-0374/ (Markdown: https://insights.sbomify.com/CVE-2002-0374/index.md)","id":"CVE-2002-0374","markdown":"https://insights.sbomify.com/CVE-2002-0374/index.md","name":"CVE-2002-0374","record":{"aliases":["GHSA-wchj-64g6-mrqx"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"unknown","non_default_config":false,"product_category":"PAM LDAP module","requires_auth":"none","summary":"Attackers can execute arbitrary code via format strings in the configuration file name of the pam_ldap PAM module.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pam_ldap","vendor":"padl_software"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Format string vulnerability in the logging function for the pam_ldap PAM LDAP module before version 144 allows attackers to execute arbitrary code via format strings in the configuration file name.","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":"Other in n/a","id":"CVE-2002-0374","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2002"},"n_packages":0,"n_references":10,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2002-0375"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2002-0373"},"products":["n/a"],"published":"2003-04-02","related":[{"cvss_score":10,"headline":"Auth bypass in n/a","id":"CVE-2003-0734","kev_date_added":null,"published":"2003-09-04"},{"cvss_score":7.5,"headline":"Privilege escalation in n/a","id":"CVE-2005-2641","kev_date_added":null,"published":"2005-08-21"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code via format strings in the configuration file name of the pam_ldap PAM module.","url":"https://insights.sbomify.com/CVE-2002-0374/"}