# CVE-2015-7243: Memory corruption in n/a

> Remote attackers can cause a crash or execute arbitrary code via a crafted WAV file in Boxoft WAV to MP3 Converter.

- **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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Sep 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7f6c-6g42-4r9g

## What is CVE-2015-7243?

CVE-2015-7243 is a high-severity memory corruption vulnerability in n/a, published on 18 Sep 2015. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in Boxoft WAV to MP3 Converter allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted WAV file.

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

## Which versions are affected by CVE-2015-7243?

It affects 1 product.


Products: Boxoft Boxoft Wav to Mp3 Converter.

## How do I fix CVE-2015-7243?

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

## Is CVE-2015-7243 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-7243 exists.

Public exploit code:

- Boxoft WAV to MP3 Converter - 'convert' Local Buffer Overflow (exploitdb)
- Boxoft WAV to MP3 Converter v1.1 Buffer Overflow (metasploit)
- Boxoft WAV to MP3 Converter 1.1 - Buffer Overflow (Metasploit) (exploitdb)
- Boxoft WAV to MP3 Converter 1.1 - Buffer Overflow (Metasploit) (exploitdb)
- Boxoft WAV to MP3 Converter 1.1 - Buffer Overflow (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-7243 and fix it if it is affected.

What it is: CVE-2015-7243 is a high-severity memory corruption vulnerability in n/a, published on 18 Sep 2015. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-7243 exists.

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-2015-7243/ (Markdown: https://insights.sbomify.com/CVE-2015-7243/index.md)
```

## Sources

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

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