CVE-2024-48091
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTally 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceTally Prime Edit Log v2.1 is vulnerable to DLL hijacking through the TextShaping.dll component. The application insecurely loads this DLL from a location an attacker can control, allowing placement of a malicious DLL that executes with the application's privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Tally Prime Edit Log installationCheck if Tally Prime Edit Log software is installed on the system by searching for it in installed programs or common installation directories (Program Files, Program Files (x86)).Affected if Tally Prime Edit Log v2.1 is installed on the system.
-
Identify installed versionRight-click the Tally Prime Edit Log executable, select Properties, and check the Details tab for the File Version. Alternatively, check the 'About' or 'Version' information within the application.Affected if The installed version is v2.1 specifically.
-
Locate TextShaping.dllSearch the Tally Prime Edit Log installation directory for the presence of TextShaping.dll file.Affected if TextShaping.dll is present in the Tally Prime Edit Log installation folder.
-
Examine DLL loading behaviorUse a tool like Process Monitor (procmon) from Sysinternals to monitor DLL loading when Tally Prime Edit Log launches. Filter for DLL name containing 'TextShaping' and check the path from which it is loaded.Affected if The application loads TextShaping.dll from a directory outside its own installation folder, such as the current working directory, system directories, or a network path.
-
Check execution locationVerify whether Tally Prime Edit Log is being launched from a network share, removable drive, or other untrusted location rather than a local secure directory.Affected if The application is run from a network share, UNC path, or other attacker-controllable location.
A user is affected if Tally Prime Edit Log v2.1 is installed and the application loads TextShaping.dll from an attacker-controllable path (outside its installation directory), particularly when run from untrusted locations.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement secure DLL loading by using full absolute paths for DLLs, enabling safe DLL search mode, or bundling the required DLL within the application directory. Users should also avoid running the application from untrusted locations such as network shares.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-48091 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-48091 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data