CVE-2009-1432
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 · uneditedSymantec Reporting Server, as used in Symantec AntiVirus (SAV) Corporate Edition 10.1 before 10.1 MR8 and 10.2 before 10.2 MR2, Symantec Client Security (SCS) before 3.1 MR8, and the Symantec Endpoint Protection Manager (SEPM) component in Symantec Endpoint Protection (SEP) before 11.0 MR2, allows remote attackers to inject arbitrary text into the login screen, and possibly conduct phishing attacks, via vectors involving a URL that is not properly handled.
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 confidenceThis is a text injection vulnerability in the Symantec Reporting Server component used across multiple Symantec enterprise security products (SAV Corporate Edition, SCS, and SEP). Attackers can inject arbitrary text into the login screen via specially crafted URLs that are not properly sanitized before display, enabling phishing attacks.
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= 10.1= 10.2= 3.1= 11.0CVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
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 Symantec Antivirus, Symantec Client Security, or Symantec Endpoint Protection installation. Look in Add/Remove Programs or the program's About dialog.Affected if Any of the three affected products (SAV, SCS, or SEP) is installed
-
Check product versionLocate the version information for the installed Symantec product through the program's interface (Help > About) or registry entries under HKLM\Software\Symantec\ or HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\Affected if Version equals exactly 10.1, 10.2, 3.1, or 11.0 for the respective product
-
Verify Reporting Server componentCheck if the Symantec Reporting Server component is installed and running. Look for services named 'Symantec Reporting Server' or 'SRS' and check for its web service listening on typical ports (or the default installation path).Affected if The Reporting Server component is present and the web interface is accessible
-
Test URL handling vulnerabilityAccess the Reporting Server login page via web browser and attempt a crafted URL with unsanitized characters in the query string (for example, appending arbitrary text after the login URL path). Observe whether the injected text appears on the login page.Affected if Arbitrary text from a crafted URL appears on the login screen without proper encoding
The environment is affected if any of the three products (SAV 10.1/10.2, SCS 3.1, or SEP 11.0) is installed with the Reporting Server web component enabled and the login page reflects unsanitized URL parameters.
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 dataUpgrade to the minimum patched versions (SAV 10.1 MR8/10.2 MR2, SCS 3.1 MR8, or SEP 11.0 MR2) or apply vendor-supplied patches to address the URL handling flaw.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-1432 — 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-1432 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