# CVE-2017-14648: Memory corruption in n/a

> A global buffer overflow in BladeEnc allows remote attackers to cause denial of service or potentially execute arbitrary code.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5h2c-vg38-fcwr

## What is CVE-2017-14648?

CVE-2017-14648 is a critical memory corruption vulnerability in n/a, published on 21 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A global buffer overflow was discovered in the iteration_loop function in loop.c in BladeEnc version 0.94.2. The vulnerability causes an out-of-bounds write, which leads to remote denial of service or possibly code execution.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2017-14648?

It affects 1 product.


Products: Bladeenc Bladeenc.

## How do I fix CVE-2017-14648?

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

## Is CVE-2017-14648 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0075](https://insights.sbomify.com/CVE-2003-0075/): Integer overflow in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-14648 and fix it if it is affected.

What it is: CVE-2017-14648 is a critical memory corruption vulnerability in n/a, published on 21 Sep 2017. 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-2017-14648 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-2017-14648/ (Markdown: https://insights.sbomify.com/CVE-2017-14648/index.md)
```

## Sources

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

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