CVE-2024-33879
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 · uneditedAn issue was discovered in VirtoSoftware Virto Bulk File Download 5.5.44 for SharePoint 2019. The Virto.SharePoint.FileDownloader/Api/Download.ashx isCompleted method allows arbitrary file download and deletion via absolute path traversal in the path parameter.
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 · high confidenceA path traversal vulnerability in the Download.ashx isCompleted method of Virto Bulk File Download 5.5.44 for SharePoint 2019 allows unauthenticated attackers to supply absolute file paths via the path parameter, enabling arbitrary file download and deletion anywhere on the server filesystem accessible to the SharePoint service account.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 5.5.44CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Identify Virto Bulk File Download installationUse SharePoint Management Shell to list installed farm solutions or check the Virto app in SharePoint Administration under Apps for SharePoint. Look for 'Virtosoftware Sharepoint Bulk File Download' or similar Virto components.Affected if The Virto Bulk File Download component is present in the SharePoint farm
-
Determine installed versionIn SharePoint Administration, navigate to the Virto app settings page or use Get-SPSolution in SharePoint Management Shell to check the installed solution version. Compare the version number to 5.5.44.Affected if The installed version is exactly 5.5.44
-
Locate Download.ashx handlerSearch the SharePoint web application directories and ISAPI folders for Download.ashx. Check the _layouts folder or any Virto-specific virtual directories under the SharePoint web root.Affected if Download.ashx exists and is accessible via the SharePoint web application
-
Verify SharePoint service account filesystem accessUsing Windows Explorer or icacls, examine the effective permissions of the SharePoint service account on critical system directories (such as C:\, Windows\System32, or other drives). Check what directories the service account can read or write.Affected if The SharePoint service account has broad filesystem permissions beyond the content databases and web application directories
The environment is affected only if Virto Bulk File Download version 5.5.44 is installed AND the Download.ashx handler is accessible, regardless of service account permissions (though excessive permissions amplify the impact).
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 dataApply vendor patch when available; as an interim measure, restrict the SharePoint service account to minimal filesystem permissions and consider network segmentation to limit exposure. Validate and sanitize all path parameters to ensure they resolve within expected directories.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33879 — 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-33879 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