{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-48091 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-48091 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-48091 is a high-severity vulnerability in n/a, published on 7 Feb 2025. 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-2024-48091 and fix it if it is affected.\n\nWhat it is: CVE-2024-48091 is a high-severity vulnerability in n/a, published on 7 Feb 2025. 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-2024-48091 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-2024-48091/ (Markdown: https://insights.sbomify.com/CVE-2024-48091/index.md)","id":"CVE-2024-48091","markdown":"https://insights.sbomify.com/CVE-2024-48091/index.md","name":"CVE-2024-48091","record":{"aliases":["GHSA-wr5v-43p3-xfrq"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Tally Prime accounting software","requires_auth":"none","summary":"Attackers can execute arbitrary code in Tally Prime Edit Log by exploiting a DLL hijacking vulnerability in TextShaping.dll.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-427","name":"Uncontrolled Search Path Element"}],"description":"Tally Prime Edit Log v2.1 was discovered to contain a DLL hijacking vulnerability via the component TextShaping.dll. This vulnerability allows attackers to execute arbitrary code via a crafted DLL.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Other in n/a","id":"CVE-2024-48091","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"File upload in n/a","id":"CVE-2024-48093"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2024-48080"},"products":["n/a"],"published":"2025-02-07","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":"total"},"state":"PUBLISHED","updated":"2025-02-10","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code in Tally Prime Edit Log by exploiting a DLL hijacking vulnerability in TextShaping.dll.","url":"https://insights.sbomify.com/CVE-2024-48091/"}