{"answers":{"affected":"3 open source packages ship an affected version, including web2py. It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-3954 in the wild and no public exploit code.","fix":"Upgrade web2py to 2.14.2 or later.","what":"CVE-2016-3954 is a medium-severity vulnerability in n/a, published on 6 Feb 2018. 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-3954 and fix it if it is affected.\n\nWhat it is: CVE-2016-3954 is a medium-severity vulnerability in n/a, published on 6 Feb 2018. 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-3954 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- web2py (PyPI): affected all versions; fixed in 2.14.2\n- web2py (PyPI): affected all versions; fixed in 2.14.2\n- web2py (PyPI): affected all versions; fixed in 2.14.2\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-3954/ (Markdown: https://insights.sbomify.com/CVE-2016-3954/index.md)","id":"CVE-2016-3954","markdown":"https://insights.sbomify.com/CVE-2016-3954/index.md","name":"CVE-2016-3954","record":{"aliases":["GHSA-jr83-vr4j-mp6p","PYSEC-2026-1062","UBUNTU-CVE-2016-3954"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"web2py framework","requires_auth":"low_privilege","summary":"Remote attackers can obtain the session cookie key via a direct request, potentially leading to further exploitation.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"web2py","vendor":"web2py"}],"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":"web2py before 2.14.2 allows remote attackers to obtain the session_cookie_key value via a direct request to examples/simple_examples/status.  NOTE: this issue can be leveraged by remote attackers to execute arbitrary code using CVE-2016-3957.","ecosystems":["PyPI"],"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":"web2py exposure of sensitive information","id":"CVE-2016-3954","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2016"},"n_packages":3,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2016-3955"},"packages":[{"ecosystem":"PyPI","fixed":["2.14.2"],"introduced":["0"],"last_affected":[],"package":"web2py","purl":null,"source":"GHSA-jr83-vr4j-mp6p"},{"ecosystem":"PyPI","fixed":["2.14.2"],"introduced":["0"],"last_affected":[],"package":"web2py","purl":"pkg:pypi/web2py","source":"GHSA-jr83-vr4j-mp6p"},{"ecosystem":"PyPI","fixed":["2.14.2"],"introduced":["0"],"last_affected":[],"package":"web2py","purl":"pkg:pypi/web2py","source":"PYSEC-2026-1062"}],"prev":{"headline":"web2py remote code execution via hardcoded encryption key in session.connect function","id":"CVE-2016-3953"},"products":["n/a"],"published":"2018-02-06","related":[{"cvss_score":9.8,"headline":"Command injection in web2py","id":"CVE-2023-45158","kev_date_added":null,"published":"2023-10-16"},{"cvss_score":9.8,"headline":"web2py remote code execution via hardcoded encryption key in session.connect function","id":"CVE-2016-3953","kev_date_added":null,"published":"2018-02-06"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2016-3957","kev_date_added":null,"published":"2018-02-06"},{"cvss_score":9.8,"headline":"web2py is vulnerable to password brute-force attack","id":"CVE-2016-10321","kev_date_added":null,"published":"2017-04-10"},{"cvss_score":8.8,"headline":"Web2py Cross-Site Request Forgery vulnerability","id":"CVE-2016-4808","kev_date_added":null,"published":"2017-01-11"},{"cvss_score":7.8,"headline":"Information disclosure in n/a","id":"CVE-2016-3952","kev_date_added":null,"published":"2018-02-06"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2016-4806","kev_date_added":null,"published":"2017-01-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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 obtain the session cookie key via a direct request, potentially leading to further exploitation.","url":"https://insights.sbomify.com/CVE-2016-3954/"}