CVE-2009-1431
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 · uneditedXFR.EXE in the Intel File Transfer service in the console in Symantec Alert Management System 2 (AMS2), as used in Symantec System Center (SSS); Symantec AntiVirus Server; Symantec AntiVirus Central Quarantine Server; Symantec AntiVirus (SAV) Corporate Edition 9 before 9.0 MR7, 10.0 and 10.1 before 10.1 MR8, and 10.2 before 10.2 MR2; Symantec Client Security (SCS) 2 before 2.0 MR7 and 3 before 3.1 MR8; and Symantec Endpoint Protection (SEP) before 11.0 MR3, allows remote attackers to execute arbitrary code by placing the code on a (1) share or (2) WebDAV server, and then sending the UNC share pathname to this service.
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 remote code execution vulnerability exists in XFR.EXE, the Intel File Transfer service in Symantec Alert Management System 2. Attackers can achieve arbitrary code execution by hosting malicious code on a network share or WebDAV server and sending the UNC path to the vulnerable service, which then loads and executes the attacker's code. This is a pre-authentication, network-based attack with high impact.
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<= 9.0>= 10, <= 10.2all versionsall versions<= 2.0>= 3.0, <= 3.1<= 11.0all versionsCVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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 installed Symantec productCheck the system for installed Symantec software by reviewing installed programs in Control Panel or querying the Windows registry under HKLM\Software\Symantec or HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall for Symantec entriesAffected if Any Symantec Antivirus, Client Security, Endpoint Protection, Central Quarantine Server, or System Center product is installed with a version matching <= 9.0, >= 10 and <= 10.2, <= 11.0, or all versions as listed in the affected versions
-
Locate XFR.EXE executableSearch for the file XFR.EXE in the Symantec program installation directory, typically found in C:\Program Files\Symantec\ or C:\Program Files\Symantec\Symantec Endpoint Protection\, or use the command: dir /s C:\XFR.EXEAffected if The XFR.EXE file exists on the system, indicating the Intel File Transfer service component is present
-
Check if Intel File Transfer service is runningOpen Services control panel or run 'sc query' command to check for a service related to XFR or File Transfer, or view running processes for XFR.EXEAffected if The XFR service is running as a process or registered service on the system
-
Verify product version against affected rangesRight-click on the installed Symantec product executable (such as symantec antivirus.exe) and select Properties, or check the version in Add/Remove Programs, then compare against the affected version ranges: SAV <= 9.0, SAV >= 10 <= 10.2, CQS all versions, SCS <= 2.0, SCS >= 3.0 <= 3.1, SEP <= 11.0Affected if The installed product version falls within any of the vulnerable version ranges specified
A system is affected if it has any of the listed Symantec products installed with a vulnerable version AND the XFR.EXE (Intel File Transfer service) component is present and running on the system.
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 · scopedApply the vendor-supplied patches (MR7 for SAV 9.x, MR8 for SAV 10.0/10.1 and SCS 2/3, MR2 for SAV 10.2, MR3 for SEP 11.0) to all affected systems. Additionally, restrict network access to the file transfer service and disable it if not required in the environment.
Apply the specific Maintenance Release (MR) patch for your product version: 9.0 MR7, 10.1 MR8, 10.2 MR2, 2.0 MR7, 3.1 MR8, or 11.0 MR3
- Identify the exact Symantec product and version installed (Antivirus Corporate Edition 9.x, 10.x, Client Security 2.x/3.x, or Endpoint Protection 11.x)
- For Symantec AntiVirus Corporate Edition 9.x: Apply patch 9.0 MR7 or later
- For Symantec AntiVirus Corporate Edition 10.0/10.1: Apply patch 10.1 MR8 or later
- For Symantec AntiVirus Corporate Edition 10.2: Apply patch 10.2 MR2 or later
- For Symantec Client Security 2.x: Apply patch 2.0 MR7 or later
- For Symantec Client Security 3.x: Apply patch 3.1 MR8 or later
- For Symantec Endpoint Protection 11.x: Apply patch 11.0 MR3 or later
- For all other affected products (Antivirus Central Quarantine Server, System Center), apply the latest available vendor patches
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-1431 — 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-2009-1431 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