# CVE-2014-2262: Memory corruption in n/a

> A buffer overflow in the SAS client allows remote attackers to execute arbitrary code if a user opens a crafted SAS program.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fwfc-m344-9jp7

## What is CVE-2014-2262?

CVE-2014-2262 is a critical memory corruption vulnerability in n/a, published on 28 Feb 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in the client application in Base SAS 9.2 TS2M3, SAS 9.3 TS1M1 and TS1M2, and SAS 9.4 TS1M0 allows user-assisted remote attackers to execute arbitrary code via a crafted SAS program.

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

## Which versions are affected by CVE-2014-2262?

It affects 1 product.


Products: Sas Base Sas.

## How do I fix CVE-2014-2262?

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

## Is CVE-2014-2262 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-14678](https://insights.sbomify.com/CVE-2019-14678/): XML external entity in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2262 and fix it if it is affected.

What it is: CVE-2014-2262 is a critical memory corruption vulnerability in n/a, published on 28 Feb 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-2262 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-2014-2262/ (Markdown: https://insights.sbomify.com/CVE-2014-2262/index.md)
```

## Sources

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

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