CVE-2025-3771
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 · uneditedA path or symbolic link manipulation vulnerability in SIR 1.0.3 and prior versions allows an authenticated non-admin local user to overwrite system files with SIR backup files, which can potentially cause a system crash. This was achieved by adding a malicious entry to the registry under the Trellix SIR registry folder or via policy or with a junction symbolic link to files that the user would not normally have permission to acces
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 confidenceA path/symlink manipulation vulnerability in SIR 1.0.3 and prior allows authenticated non-admin local users to overwrite system files by adding malicious registry entries under the Trellix SIR registry folder or via junction symbolic links to files they normally cannot access, potentially causing system crashes.
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<= 1.0.3CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 if Trellix System Information Reporter is installedCheck for SIR installation by searching program files directories or querying installed programs via Windows Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or using 'Get-ItemProperty' PowerShell command for installed software listingAffected if Trellix SIR version 1.0.3 or lower is found installed on the system
-
Determine the installed SIR versionLocate the SIR executable (typically named SIR.exe or similar under Program Files/Trellix) and right-click to view Properties > Details, or run 'Get-ItemProperty -Path "C:\Program Files\Trellix\SIR\SIR.exe" | Select-Object VersionInfo'Affected if The version shown is 1.0.3 or any version prior to 1.0.3
-
Verify permissions on SIR registry keysOpen Registry Editor and navigate to HKLM\SOFTWARE\Trellix\SIR (or HKCU\SOFTWARE\Trellix\SIR if present), right-click the key, select Permissions, and verify which users have Write or Full Control permissionsAffected if Authenticated non-admin users are granted Write or Full Control permissions to SIR registry keys
-
Inspect for unauthorized junction points or symbolic linksOpen Command Prompt as administrator and run 'mklink /d' or use 'dir /AL /S C:\' to search for alternate data streams and junction points in SIR directories, or manually check the SIR installation folder and backup directories for suspicious symbolic linksAffected if Unexpected junction points or symbolic links are found pointing outside the SIR installation directory or to system-protected locations
-
Audit SIR-related registry entries for tamperingReview registry keys under HKLM\SOFTWARE\Trellix\SIR and HKCU\SOFTWARE\Trellix\SIR for unexpected or newly added values, particularly those containing paths to executable files or scripts, using 'reg query HKLM\SOFTWARE\Trellix\SIR'Affected if Registry entries contain unexpected paths, point to user-writable locations, or show signs of unauthorized modification
The system is affected if Trellix System Information Reporter version 1.0.3 or lower is installed AND non-admin users have Write access to SIR registry keys or the application directories, allowing potential symlink or registry-based manipulation.
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 dataRestrict non-admin user permissions to SIR registry keys and backup directories, and monitor for unauthorized modifications to SIR-related registry entries and symlinks.
- Consultation6.0 h
- Implementation10.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3771 — 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-2025-3771 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