CVE-2005-1107
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 · uneditedMcAfee Internet Security Suite 2005 uses insecure default ACLs for installed files, which allows local users to gain privileges or disable protection by modifying certain files.
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 confidenceMcAfee Internet Security Suite 2005 ships with insecure default Access Control Lists (ACLs) on installed files, allowing local non-privileged users to modify security-critical files. This permission misconfiguration enables local privilege escalation or the ability to disable the security software entirely by overwriting protected executables or configuration files.
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= 2005CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
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 McAfee Internet Security Suite 2005 is installedCheck the installed programs list in Windows Add/Remove Programs or use 'wmic product' to list installed software and look for 'McAfee Internet Security Suite 2005'Affected if The product 'McAfee Internet Security Suite 2005' version 2005 is present on the system
-
Locate the McAfee installation directoryCheck the default installation path typically under 'C:\Program Files\McAfee\' or 'C:\Program Files (x86)\McAfee\', or right-click the McAfee shortcut and check Properties for the executable pathAffected if The installation directory exists on the system
-
Examine ACLs on the McAfee installation folderRight-click the McAfee installation folder in Windows Explorer, go to Properties > Security tab, and review the permissions for Users and Everyone groups. Alternatively, use 'icacls "C:\Program Files\McAfee"' from an elevated command promptAffected if Users or non-admin accounts are granted Write or Full Control permissions to the installation directory or its subfolders
-
Check write access to security-critical executablesAttempt to modify or delete a key executable file in the McAfee program folder (such as .exe files in the main directory) using a standard non-admin user account, or inspect ACLs on specific executable filesAffected if Non-privileged users can write to or modify executable files within the McAfee installation directory
-
Verify ownership of security-critical filesCheck the owner of executable and configuration files in the McAfee folder by reviewing the Security tab > Advanced > Owner, or using 'icacls' with the /owner flagAffected if Files are owned by a non-administrator user or by Users group rather than SYSTEM or Administrators
A user is affected if McAfee Internet Security Suite 2005 is installed AND non-privileged accounts have Write or Full Control permissions to the program files directory or its executables.
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 file permissions on security software installation directories to administrator-only write access; verify all executable and configuration files are owned by SYSTEM with restricted ACLs following the principle of least privilege.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-1107 — 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-2005-1107 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