{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-45925 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-45925 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-45925 is a 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-45925 and fix it if it is affected.\n\nWhat it is: CVE-2023-45925 is a 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-45925 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-45925/ (Markdown: https://insights.sbomify.com/CVE-2023-45925/index.md)","id":"CVE-2023-45925","markdown":"https://insights.sbomify.com/CVE-2023-45925/index.md","name":"CVE-2023-45925","record":{"aliases":["DEBIAN-CVE-2023-45925","GHSA-q22h-9rc9-jpmp"],"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":"GNU Midnight Commander","requires_auth":"none","summary":"A NULL pointer dereference in GNU Midnight Commander can cause a crash, though it is disputed as a usability issue.","user_interaction":"required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"GNU Midnight Commander 4.8.29-146-g299d9a2fb was discovered to contain a NULL pointer dereference via the function x_error_handler() at tty/x11conn.c. NOTE: this is disputed because it should be categorized as a usability problem (an X operation silently fails).","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":"Null dereference in n/a","id":"CVE-2023-45925","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":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2023-45926"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2023-45924"},"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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-04","vendors":["n/a"]},"summary":"A NULL pointer dereference in GNU Midnight Commander can cause a crash, though it is disputed as a usability issue.","url":"https://insights.sbomify.com/CVE-2023-45925/"}