{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-3111 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2016-3111 is a medium-severity vulnerability in n/a, published on 8 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-3111 and fix it if it is affected.\n\nWhat it is: CVE-2016-3111 is a medium-severity vulnerability in n/a, published on 8 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-3111 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-3111/ (Markdown: https://insights.sbomify.com/CVE-2016-3111/index.md)","id":"CVE-2016-3111","markdown":"https://insights.sbomify.com/CVE-2016-3111/index.md","name":"CVE-2016-3111","record":{"aliases":["GHSA-fgrp-5xv9-qv52"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Pulp content management","requires_auth":"low_privilege","summary":"Local attackers can read RSA keys during Pulp installation due to world-readable permissions, compromising message validation between server and consumers.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"pulp","vendor":"pulpproject"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"pulp.spec in the installation process for Pulp 2.8.3 generates the RSA key pairs used to validate messages between the pulp server and pulp consumers in a directory that is world-readable before later modifying the permissions, which might allow local users to read the generated RSA keys via reading the key files while the installation process is running.","ecosystems":[],"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":"Information disclosure in n/a","id":"CVE-2016-3111","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2016"},"n_packages":0,"n_references":9,"next":{"headline":"Information disclosure in n/a","id":"CVE-2016-3112"},"packages":[],"prev":{"headline":"mod_cluster Denial of Service vulnerability","id":"CVE-2016-3110"},"products":["n/a"],"published":"2017-06-08","related":[{"cvss_score":8.1,"headline":"Security feature bypass in n/a","id":"CVE-2015-5263","kev_date_added":null,"published":"2017-09-25"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2016-3112","kev_date_added":null,"published":"2017-06-08"},{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2013-7450","kev_date_added":null,"published":"2017-04-03"},{"cvss_score":7.1,"headline":"Path traversal in n/a","id":"CVE-2016-3108","kev_date_added":null,"published":"2017-06-08"},{"cvss_score":6.8,"headline":"Path traversal in pulp","id":"CVE-2018-10917","kev_date_added":null,"published":"2018-08-15"},{"cvss_score":6.7,"headline":"Pulpcore: rbac permissions incorrectly assigned in tasks that create objects","id":"CVE-2024-7143","kev_date_added":null,"published":"2024-08-07"},{"cvss_score":5.5,"headline":"Information disclosure in n/a","id":"CVE-2016-3107","kev_date_added":null,"published":"2017-06-08"}],"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-08-05","vendors":["n/a"]},"summary":"Local attackers can read RSA keys during Pulp installation due to world-readable permissions, compromising message validation between server and consumers.","url":"https://insights.sbomify.com/CVE-2016-3111/"}