{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-46051 in the wild and no public exploit code.","fix":"No fix published yet.","what":"CVE-2023-46051 is a low-severity vulnerability in n/a, published on 27 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-46051 and fix it if it is affected.\n\nWhat it is: CVE-2023-46051 is a low-severity vulnerability in n/a, published on 27 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-46051 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-2023-46051/ (Markdown: https://insights.sbomify.com/CVE-2023-46051/index.md)","id":"CVE-2023-46051","markdown":"https://insights.sbomify.com/CVE-2023-46051/index.md","name":"CVE-2023-46051","record":{"aliases":["DEBIAN-CVE-2023-46051","ECHO-e2ea-59e2-c0ed","GHSA-pjw3-8x26-xpwm"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TeX Live typesetting","requires_auth":"none","summary":"A NULL pointer dereference in TeX Live may cause a denial of service, though the issue is disputed as a usability problem.","user_interaction":"required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":3.3,"severity":"low","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"TeX Live 944e257 allows a NULL pointer dereference in texk/web2c/pdftexdir/tounicode.c. NOTE: this is disputed because it should be categorized as a usability problem.","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":"Null dereference in n/a","id":"CVE-2023-46051","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2023-46052"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2023-46050"},"products":["n/a"],"published":"2024-03-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-04","vendors":["n/a"]},"summary":"A NULL pointer dereference in TeX Live may cause a denial of service, though the issue is disputed as a usability problem.","url":"https://insights.sbomify.com/CVE-2023-46051/"}