# CVE-2013-2220: Memory corruption in n/a

> Remote attackers can cause a crash or execute arbitrary code via a buffer overflow in the PHP Radius extension.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Jul 2013
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2013-2220, DSA-2726-1, GHSA-4x5w-qg6w-8rqm, MGASA-2013-0206

## What is CVE-2013-2220?

CVE-2013-2220 is a high-severity memory corruption vulnerability in n/a, published on 31 Jul 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the radius_get_vendor_attr function in the Radius extension before 1.2.7 for PHP allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a large Vendor Specific Attributes (VSA) length value.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Radius Extension Project Radius.

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

Upgrade to a fixed version.

## Is CVE-2013-2220 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-2220 is a high-severity memory corruption vulnerability in n/a, published on 31 Jul 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-2220 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-2220/ (Markdown: https://insights.sbomify.com/CVE-2013-2220/index.md)
```

## Sources

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

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