{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51277 exists.","fix":"No fix has been published for CVE-2023-51277 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-51277 is a critical vulnerability in n/a, published on 5 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-51277 and fix it if it is affected.\n\nWhat it is: CVE-2023-51277 is a critical vulnerability in n/a, published on 5 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51277 exists.\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-2023-51277/ (Markdown: https://insights.sbomify.com/CVE-2023-51277/index.md)","id":"CVE-2023-51277","markdown":"https://insights.sbomify.com/CVE-2023-51277/index.md","name":"CVE-2023-51277","record":{"aliases":["GHSA-h93h-6948-g84m"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Jupyter Notebook Viewer","requires_auth":"none","summary":"Attackers can bypass macOS security restrictions in Jupyter Notebook Viewer release builds due to the get-task-allow entitlement.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jupyter_notebook_viewer","vendor":"tinowagner"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","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":"nbviewer-app (aka Jupyter Notebook Viewer) before 0.1.6 has the get-task-allow entitlement for release builds.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Security feature bypass in n/a","id":"CVE-2023-51277","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2023-51281"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2023-51258"},"products":["n/a"],"published":"2024-01-05","related":[],"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-06-03","vendors":["n/a"]},"summary":"Attackers can bypass macOS security restrictions in Jupyter Notebook Viewer release builds due to the get-task-allow entitlement.","url":"https://insights.sbomify.com/CVE-2023-51277/"}