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

> Remote attackers can cause a crash or execute arbitrary code in the BOINC client by exploiting a format string vulnerability in account file processing.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **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:** Yes
- **Published:** 2 Jun 2014
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2013-7386, GHSA-gf7f-q52v-9537

## What is CVE-2013-7386?

CVE-2013-7386 is a medium-severity memory corruption vulnerability in n/a, published on 2 Jun 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

Format string vulnerability in the PROJECT::write_account_file function in client/cs_account.cpp in BOINC, possibly 7.2.33, allows remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via format string specifiers in the gui_urls item in an account file.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

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

It affects 1 product.


Products: Universityofcalifornia Boinc Client.

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

Upgrade to a fixed version.

## Is CVE-2013-7386 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-2018](https://insights.sbomify.com/CVE-2013-2018/): SQL injection in BOINC (critical 9.8)
- [CVE-2013-2019](https://insights.sbomify.com/CVE-2013-2019/): Memory corruption in n/a (critical 9.3)
- [CVE-2013-2298](https://insights.sbomify.com/CVE-2013-2298/): Memory corruption in n/a (critical 9.3)
- [CVE-2011-5280](https://insights.sbomify.com/CVE-2011-5280/): Memory corruption in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-7386 is a medium-severity memory corruption vulnerability in n/a, published on 2 Jun 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-2013-7386 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-7386/ (Markdown: https://insights.sbomify.com/CVE-2013-7386/index.md)
```

## Sources

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

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