CVE-2024-45207
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 · uneditedDLL injection in Veeam Agent for Windows can occur if the system's PATH variable includes insecure locations. When the agent runs, it searches these directories for necessary DLLs. If an attacker places a malicious DLL in one of these directories, the Veeam Agent might load it inadvertently, allowing the attacker to execute harmful code. This could lead to unauthorized access, data theft, or disruption of services
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 confidenceDLL search order hijacking vulnerability in Veeam Agent for Windows where the agent searches directories in the system PATH variable for DLLs. If an attacker places a malicious DLL in an insecure PATH directory (such as a world-writable temp folder), the agent will inadvertently load it, enabling arbitrary code execution with the agent's privileges.
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>= 6.0.0.959, < 6.3.0.177CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:H/PR:L/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.
-
Check installed Veeam Agent for Windows versionOpen Control Panel > Programs and Features, find 'Veeam Agent for Windows', or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like '*Veeam*'} | Select-Object DisplayName, DisplayVersion' in PowerShellAffected if Version is 6.0.0.959 through 6.3.0.176 (any version >= 6.0.0.959 and < 6.3.0.177)
-
Verify Veeam Agent service is runningOpen Services console (services.msc) and check if 'Veeam Agent for Windows' service exists and is running, or run 'Get-Service Veeam*' in PowerShellAffected if The Veeam Agent service is installed and running - only then can it be exploited
-
Examine system PATH for insecure directoriesRun 'echo $env:PATH' in PowerShell or check System Properties > Environment Variables > System variables > PATH. Look for directories like %TEMP%, %TMP%, %USERPROFILE%, or any world-writable locationsAffected if PATH contains world-writable directories such as %TEMP% or %TMP% (especially if these are accessible to untrusted users)
-
Check for DLL files in PATH temp directoriesRun 'Get-ChildItem $env:TEMP -Filter *.dll -ErrorAction SilentlyContinue' and similar for other temp paths in your PATHAffected if Any DLL files exist in temp directories that are also in the system PATH
A system is affected if Veeam Agent for Windows version 6.0.0.959-6.3.0.176 is installed and running, and the system PATH contains insecure world-writable directories (like %TEMP% or %TMP%) that could be used to place a malicious DLL.
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.
dbcve · scoped6.3.0.177
Remove insecure directories (particularly world-writable locations like %TEMP%, %TMP%, or untrusted network shares) from the system PATH variable, and ensure Veeam Agent uses secure, controlled DLL search paths or absolute paths for required DLLs.
Veeam Agent for Windows 6.3.0.177 or later
- Verify the current installed version of Veeam Agent for Windows by opening the application and checking About, or via Programs and Features
- Download the latest version of Veeam Agent for Windows (version 6.3.0.177 or later) from the official Veeam download page at www.veeam.com
- Close any running instances of Veeam Agent for Windows before upgrading
- Run the installer with administrator privileges
- Follow the on-screen installation wizard prompts to complete the upgrade
- Restart the computer if prompted by the installer
- After upgrade, verify the new version is installed correctly
- As a supplementary hardening measure, review and sanitize the system PATH environment variable to remove any insecure or unnecessary directories (e.g., user-writable directories, removable media paths)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45207 — 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-45207 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