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

> Remote attackers can cause a denial of service by sending crafted BGP updates to devices configured with 4-byte AS numbers.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-85q6-7xq9-8qqf

## What is CVE-2014-3818?

CVE-2014-3818 is a high-severity memory corruption vulnerability in Juniper Junos, published on 14 Oct 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Juniper Junos OS 9.1 through 11.4 before 11.4R11, 12.1 before R10, 12.1X44 before D40, 12.1X46 before D30, 12.1X47 before D11 and 12.147-D15, 12.1X48 before D41 and D62, 12.2 before R8, 12.2X50 before D70, 12.3 before R6, 13.1 before R4-S2, 13.1X49 before D49, 13.1X50 before 30, 13.2 before R4, 13.2X50 before D20, 13.2X51 before D25, 13.2X52 before D15, 13.3 before R2, and 14.1 before R1, when supporting 4-byte AS numbers and a BGP peer does not, allows remote attackers to cause a denial of service (memory corruption and RDP routing process crash and restart) via crafted transitive attributes in a BGP UPDATE.

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

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

It affects 1 product.


Products: Juniper Junos.

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

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

## Is CVE-2014-3818 being exploited?

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

## Other vulnerabilities in Juniper Junos

- [CVE-2023-36845](https://insights.sbomify.com/CVE-2023-36845/): Juniper Junos OS EX Series and SRX Series PHP External Variable Modification (critical 9.8, exploited in the wild)
- [CVE-2020-1631](https://insights.sbomify.com/CVE-2020-1631/): Juniper Junos OS Path Traversal (high 8.8, exploited in the wild)
- [CVE-2025-21590](https://insights.sbomify.com/CVE-2025-21590/): Juniper Junos OS Improper Isolation or Compartmentalization (medium 6.7, exploited in the wild)
- [CVE-2023-36851](https://insights.sbomify.com/CVE-2023-36851/): Juniper Junos OS SRX Series Missing Authentication for Critical Function (medium 5.3, exploited in the wild)
- [CVE-2023-36844](https://insights.sbomify.com/CVE-2023-36844/): Juniper Junos OS EX Series PHP External Variable Modification (medium 5.3, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-3818 is a high-severity memory corruption vulnerability in Juniper Junos, published on 14 Oct 2014. 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-2014-3818 in the wild and no public exploit code.

Affected product: Juniper Junos. 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-3818/ (Markdown: https://insights.sbomify.com/CVE-2014-3818/index.md)
```

## Sources

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

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