{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2016-6342 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-6342 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-6342 is a high-severity missing authorization vulnerability in Fedoraproject Fedora, published on 27 Jun 2017. 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-6342 and fix it if it is affected.\n\nWhat it is: CVE-2016-6342 is a high-severity missing authorization vulnerability in Fedoraproject Fedora, published on 27 Jun 2017. 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-6342 in the wild and no public exploit code.\n\nAffected product: Fedoraproject Fedora. 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-6342/ (Markdown: https://insights.sbomify.com/CVE-2016-6342/index.md)","id":"CVE-2016-6342","markdown":"https://insights.sbomify.com/CVE-2016-6342/index.md","name":"CVE-2016-6342","record":{"aliases":["GHSA-qfxm-h9jr-5w92","UBUNTU-CVE-2016-6342"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"elog logbook","requires_auth":"none","summary":"Remote attackers can post data as any username in the elog logbook due to missing authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"elog","vendor":"elog_project"},{"product":"fedora","vendor":"fedoraproject"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"elog 3.1.1 allows remote attackers to post data as any username in the logbook.","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":"Missing authorization in n/a","id":"CVE-2016-6342","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"fedoraproject:fedora","products":["fedoraproject:fedora"],"type":"missing_authorization","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in Dashbuilder","id":"CVE-2016-6343"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2016-6341"},"products":["n/a"],"published":"2017-06-27","related":[{"cvss_score":9.3,"headline":"ELOG configuration file authorization bypass","id":"CVE-2025-64348","kev_date_added":null,"published":"2025-10-31"},{"cvss_score":8.7,"headline":"ELOG user profile missing authorization","id":"CVE-2025-64349","kev_date_added":null,"published":"2025-10-31"},{"cvss_score":8.6,"headline":"ELOG file upload stored XSS","id":"CVE-2025-62618","kev_date_added":null,"published":"2025-10-31"},{"cvss_score":7.5,"headline":"Information disclosure in ELOG","id":"CVE-2019-3992","kev_date_added":null,"published":"2019-12-17"},{"cvss_score":7.5,"headline":"Information disclosure in ELOG","id":"CVE-2019-3993","kev_date_added":null,"published":"2019-12-17"},{"cvss_score":7.5,"headline":"Use after free in ELOG","id":"CVE-2019-3994","kev_date_added":null,"published":"2019-12-17"},{"cvss_score":7.5,"headline":"Null dereference in ELOG","id":"CVE-2019-3995","kev_date_added":null,"published":"2019-12-17"}],"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-06","vendors":["n/a"]},"summary":"Remote attackers can post data as any username in the elog logbook due to missing authorization checks.","url":"https://insights.sbomify.com/CVE-2016-6342/"}