CVE-2015-6548
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 · uneditedMultiple SQL injection vulnerabilities in a PHP script in the management console on Symantec Web Gateway (SWG) appliances with software before 5.2.2 DB 5.0.0.1277 allow 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 vulnerabilities exist in the PHP-based management console of Symantec Web Gateway appliances. The flaws allow remote authenticated users to inject arbitrary SQL commands through unspecified vectors in the web interface, potentially enabling data exfiltration or database compromise.
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<= 5.2.2CVSS 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
- Multiple
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:M/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 Symantec Web Gateway installationIdentify if the Symantec Web Gateway appliance or software is deployed in your environment. This is typically a network appliance or virtual appliance. Check your asset inventory or network scans for the product name.Affected if Symantec Web Gateway is installed and the version cannot be determined or is confirmed as 5.2.2 or lower
-
Determine installed versionAccess the management console or check system documentation for the installed version number. The affected version range is 5.2.2 and below. Compare your installed version against this threshold.Affected if Installed version is 5.2.2 or any earlier version of Symantec Web Gateway
-
Verify management console accessibilityCheck if the PHP-based management console (typically accessible via HTTP/HTTPS on port 443 or 80) is reachable from network segments outside your trusted administrative zone.Affected if The management console is exposed to untrusted network segments or the internet
-
Assess authentication configurationReview access controls for the management console. Determine whether default or weak credentials are in use, or whether IP-based access restrictions are enforced.Affected if The console is accessible remotely with minimal or default authentication, or no IP allowlist is configured for administrative access
Your environment is affected if you are running Symantec Web Gateway version 5.2.2 or lower and the management console is accessible to remote users with authentication capabilities.
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 dataApply the vendor patch (version 5.2.2 DB 5.0.0.1277 or later) which addresses the SQL injection flaws. If patching is not possible, restrict management console access to trusted IP addresses and enforce strong credential policies.
- Consultation2.0 h
- Testing4.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 $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6548 — 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-6548 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