dbcve.org
Web GatewayApplication · Symantec

CVE-2013-5017

CRITICAL · 9.8 CVSS v3.0 Published 2014-06-18
Fix available
A fix is available. Upgrade to after 5.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
SNMPConfig.php in the management console in Symantec Web Gateway (SWG) before 5.2.1 allows remote attackers to execute arbitrary 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 confidence

A command injection vulnerability in SNMPConfig.php within the Symantec Web Gateway management console allows remote attackers to execute arbitrary operating system commands. The vulnerability is exploitable without authentication due to insufficient input validation, and the critical CVSS score of 9.8 reflects its ease of exploitation and complete impact on confidentiality and integrity.

MitigationUpgrade Symantec Web Gateway to version 5.2.1 or later. If immediate patching is not feasible, restrict network access to the management console to trusted IP addresses and consider deploying a web application firewall to block exploitation attempts.

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
Web GatewayApplication
Affected:<= 5.2

CVSS 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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Symantec Web Gateway is installed
    Check for the presence of the application by looking for the SNMPConfig.php file in the web directory, typically in /var/www/html/ or the web root. Use: find /var/www -name SNMPConfig.php 2>/dev/null or check your web server document root.
    Affected if The file SNMPConfig.php exists in the web application directory and the application is running.
  2. Determine the installed version of Symantec Web Gateway
    Check the version by examining the release notes, the about page in the management console, or by looking for version files in the installation directory. Compare your version against the affected range of <= 5.2.
    Affected if The installed version is 5.2 or any earlier version (5.0, 4.x, etc.).
  3. Verify the SNMP configuration interface is accessible
    Confirm the management console is reachable by accessing the SNMPConfig.php page via HTTP/HTTPS, typically at a URL like https://your-server/snmp/ SNMPConfig.php or through the main management interface.
    Affected if The SNMPConfig.php page loads and accepts user input for SNMP configuration settings.
  4. Check if the management console is exposed to the network
    Review firewall rules or network access controls to determine if the web management interface is accessible from untrusted networks. Use netstat or similar tools to check listening ports (80, 443).
    Affected if The management console (port 80/443) is bound to 0.0.0.0 or an exposed network interface without IP restrictions.

You are affected if Symantec Web Gateway version 5.2 or lower is installed and the SNMPConfig.php management interface is accessible on the network, since the vulnerability allows unauthenticated remote command execution through this file.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 5.2
Interim mitigation

Upgrade Symantec Web Gateway to version 5.2.1 or later. If immediate patching is not feasible, restrict network access to the management console to trusted IP addresses and consider deploying a web application firewall to block exploitation attempts.

Recommended fix High confidence

5.2.1

  1. Download Symantec Web Gateway version 5.2.1 or later from the official Symantec support portal
  2. Backup the current configuration of the Web Gateway appliance
  3. Consult the Symantec Web Gateway upgrade documentation for detailed instructions
  4. Perform the upgrade following the documented procedure
  5. Verify the SNMPConfig.php vulnerability is no longer present by checking the version number
  6. Confirm normal operation of the management console and all services
Caveat Review release notes for any configuration changes required between versions; test in staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Web Gateway Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-5017 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-5017 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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