CVE-2010-0115
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 login.php in the GUI management console in Symantec Web Gateway 4.5 before 4.5.0.376 allows remote attackers to execute arbitrary SQL commands via the USERNAME parameter.
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 confidenceSQL injection vulnerability in the login.php authentication form of Symantec Web Gateway 4.5 allows remote attackers to inject arbitrary SQL commands via the USERNAME parameter. Successful exploitation bypasses authentication and may expose or manipulate backend database contents.
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= 4.5= 4.5.0.325= 4.5.0.326= 4.5.0.327CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/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.
-
Identify the installed Symantec Web Gateway versionAccess the administrative web interface or check the product documentation/system info page for the exact version number. If you have CLI access, check the about page or version file in the installation directory.Affected if The version matches 4.5, 4.5.0.325, 4.5.0.326, or 4.5.0.327 exactly.
-
Confirm the login.php endpoint is accessibleAttempt to access the login page via HTTP/HTTPS at the typical path /login.php or /admin/login.php on the Symantec Web Gateway web interface.Affected if The login.php page is reachable and responds to requests.
-
Verify the USERNAME parameter accepts inputSubmit a test login request to login.php with a crafted USERNAME parameter (e.g., using a single quote or SQL meta-character) and observe if the application returns a database error or unusual response.Affected if The USERNAME parameter reflects input in an unsafe manner or produces SQL syntax errors in the response.
-
Check for unauthorized access indicatorsReview web server access logs and application logs for SQL injection patterns in the USERNAME parameter, such as quotes, UNION SELECT, OR 1=1, or other SQL keywords.Affected if Suspicious SQL injection payloads appear in logs for the login.php USERNAME parameter.
You are affected if the installed version is exactly 4.5, 4.5.0.325, 4.5.0.326, or 4.5.0.327 and the web login interface is accessible and exposed.
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 Web Gateway 4.5.0.376 or later. If immediate patching is not possible, implement web application firewall rules to block SQL injection payloads in the login parameters as a temporary mitigation.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0115 — 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-2010-0115 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