# CVE-2018-6948: Memory corruption in n/a

> A buffer overflow in CCN-lite allows attackers to execute arbitrary code or cause denial of service by sending crafted NFN-R2C packets when NFN is enabled.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 13 Feb 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-mv8v-xw3m-x43j

## What is CVE-2018-6948?

CVE-2018-6948 is a critical memory corruption vulnerability in n/a, published on 13 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In CCN-lite 2, the function ccnl_prefix_to_str_detailed can cause a buffer overflow, when writing a prefix to the buffer buf. The maximal size of the prefix is CCNL_MAX_PREFIX_SIZE; the buffer has the size CCNL_MAX_PREFIX_SIZE. However, when NFN is enabled, additional characters are written to the buffer (e.g., the "NFN" and "R2C" tags). Therefore, sending an NFN-R2C packet with a prefix of size CCNL_MAX_PREFIX_SIZE can cause an overflow of buf inside ccnl_prefix_to_str_detailed.

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

## Which versions are affected by CVE-2018-6948?

It affects 1 product.


Products: Ccn-Lite Ccn-Lite.

## How do I fix CVE-2018-6948?

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

## Is CVE-2018-6948 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-12889](https://insights.sbomify.com/CVE-2018-12889/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-7039](https://insights.sbomify.com/CVE-2018-7039/): Integer overflow in n/a (critical 9.8)
- [CVE-2018-6953](https://insights.sbomify.com/CVE-2018-6953/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-12465](https://insights.sbomify.com/CVE-2017-12465/): Multiple integer overflows in CCN-lite before 2.00 allow context-dependent attackers to have unspecified impact via vectors involving the (1 (critical 9.8)
- [CVE-2017-12466](https://insights.sbomify.com/CVE-2017-12466/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-6948 and fix it if it is affected.

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

## Sources

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

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