CVE-2015-1491
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 · uneditedSQL injection vulnerability in the management console in Symantec Endpoint Protection Manager (SEPM) 12.1 before 12.1-RU6-MP1 allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors.
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 confidenceSQL injection vulnerability in the management console of Symantec Endpoint Protection Manager (SEPM) 12.1 prior to version 12.1-RU6-MP1 allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors in the management interface.
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= 12.1.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
- M
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:S/C:P/I:P/A:P
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.
-
Confirm SEPM installationLocate the Symantec Endpoint Protection Manager installation directory, typically found at C:\Program Files\Symantec\Symantec Endpoint Protection Manager on Windows servers where SEPM is deployed.Affected if SEPM is not installed on the system.
-
Check SEPM versionOpen the management console and navigate to Help > About, or check the version displayed on the SEPM login page. Alternatively, check the version info in the SEPM installation directory or via Windows Programs and Features.Affected if The version is 12.1.0 through 12.1-RU6 (any build prior to 12.1-RU6-MP1).
-
Verify management console is accessibleAttempt to access the SEPM management console URL (default ports 8445 or 443) on the server where SEPM is installed. Confirm the console responds to HTTP/HTTPS requests.Affected if The management console is enabled and network-accessible, combined with a vulnerable version.
-
Confirm management console users existCheck if any administrator or operator accounts are configured in SEPM by logging into the management console and reviewing Accounts > Administrators, or check the sem5.db SQLite database in the SEPM data directory for user entries.Affected if Any authenticated user accounts exist in SEPM, which would provide the authentication vector for exploiting this SQL injection.
The environment is affected if Symantec Endpoint Protection Manager version 12.1.0 through 12.1-RU6 is installed with the management console accessible and configured with at least one user account.
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 Symantec Endpoint Protection Manager 12.1-RU6-MP1 or later to remediate this vulnerability.
- Consultation2.0 h
- Implementation4.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1491 — 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-2015-1491 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