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

> Authenticated users with specific permissions can escalate privileges or cause denial of service in Apache VCL due to improper data validation.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Feb 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-c993-cxr3-5g3p

## What is CVE-2013-0267?

CVE-2013-0267 is a high-severity vulnerability in n/a, published on 21 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Privileges portion of the web GUI and the XMLRPC API in Apache VCL 2.3.x before 2.3.2, 2.2.x before 2.2.2 and 2.1 allow remote authenticated users with nodeAdmin, manageGroup, resourceGrant, or userGrant permissions to gain privileges, cause a denial of service, or conduct cross-site scripting (XSS) attacks by leveraging improper data validation.

Weakness: CWE-264, CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Apache Vcl.

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

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

## Is CVE-2013-0267 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-53679](https://insights.sbomify.com/CVE-2024-53679/): Apache VCL: XSS vulnerability in User Lookup impacting user privileges (high 8.4)
- [CVE-2024-53678](https://insights.sbomify.com/CVE-2024-53678/): Apache VCL: SQL injection vulnerability in New Block Allocation form (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-0267 is a high-severity vulnerability in n/a, published on 21 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-0267 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-0267/ (Markdown: https://insights.sbomify.com/CVE-2013-0267/index.md)
```

## Sources

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

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