{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-20014 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-20014 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-20014 is a critical vulnerability in n/a, published on 21 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-20014 and fix it if it is affected.\n\nWhat it is: CVE-2016-20014 is a critical vulnerability in n/a, published on 21 Apr 2022. 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-2016-20014 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-2016-20014/ (Markdown: https://insights.sbomify.com/CVE-2016-20014/index.md)","id":"CVE-2016-20014","markdown":"https://insights.sbomify.com/CVE-2016-20014/index.md","name":"CVE-2016-20014","record":{"aliases":["GHSA-85mx-crqg-rfwj","UBUNTU-CVE-2016-20014"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"PAM TACACS+ library","requires_auth":"none","summary":"An attacker can read sensitive memory data because the PAM TACACS+ library fails to clear authentication response structures.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pam_tacplus","vendor":"pam_tacplus_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In pam_tacplus.c in pam_tacplus before 1.4.1, pam_sm_acct_mgmt does not zero out the arep data structure.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Information disclosure in n/a","id":"CVE-2016-20014","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2016"},"n_packages":0,"n_references":1,"next":{"headline":"Race condition in n/a","id":"CVE-2016-20015"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2016-20013"},"products":["n/a"],"published":"2022-04-21","related":[{"cvss_score":9.8,"headline":"Weak cryptography in n/a","id":"CVE-2020-27743","kev_date_added":null,"published":"2020-10-26"}],"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-06","vendors":["n/a"]},"summary":"An attacker can read sensitive memory data because the PAM TACACS+ library fails to clear authentication response structures.","url":"https://insights.sbomify.com/CVE-2016-20014/"}