# CVE-2013-4672: Privilege escalation in n/a

> Local users can bypass access restrictions and escalate privileges on Symantec Web Gateway appliances due to incorrect sudoers configuration.

- **Severity:** High 7.2 (`AV:A/AC:L/Au:M/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9pwg-54q3-m94v

## What is CVE-2013-4672?

CVE-2013-4672 is a high-severity vulnerability in n/a, published on 31 Jul 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The management console on the Symantec Web Gateway (SWG) appliance before 5.1.1 has an incorrect sudoers file, which allows local users to bypass intended access restrictions via a command.

Weakness: CWE-264

## Which versions are affected by CVE-2013-4672?

It affects 3 products.


Products: Symantec Web Gateway, Symantec Web Gateway Appliance 8450, Symantec Web Gateway Appliance 8490.

## How do I fix CVE-2013-4672?

No fix has been published for CVE-2013-4672 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-4672 being exploited?

There is no known exploitation of CVE-2013-4672 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2012-2953](https://insights.sbomify.com/CVE-2012-2953/): Command injection in n/a (critical 10.0)
- [CVE-2012-2976](https://insights.sbomify.com/CVE-2012-2976/): Command injection in n/a (critical 10.0)
- [CVE-2012-0297](https://insights.sbomify.com/CVE-2012-0297/): Code injection in n/a (critical 10.0)
- [CVE-2012-0299](https://insights.sbomify.com/CVE-2012-0299/): File upload in n/a (critical 10.0)
- [CVE-2013-5017](https://insights.sbomify.com/CVE-2013-5017/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4672 and fix it if it is affected.

What it is: CVE-2013-4672 is a high-severity vulnerability in n/a, published on 31 Jul 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-4672 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-4672/ (Markdown: https://insights.sbomify.com/CVE-2013-4672/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-4672
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-4672
- OSV: https://osv.dev/vulnerability/CVE-2013-4672

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-4672/
Summaries are generated and may contain mistakes; the official description above is the record.