# CVE-2019-0071: Junos OS: EX2300, EX3400 Series: Veriexec signature checking not enforced in specific versions of Junos OS

> A flaw in Junos OS disables Veriexec file integrity checking, allowing local users to install untrusted binaries and escalate privileges.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-8rxr-vx8g-7w4h

## What is CVE-2019-0071?

CVE-2019-0071 is a high-severity vulnerability in Juniper Junos, published on 9 Oct 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Veriexec is a kernel-based file integrity subsystem in Junos OS that ensures only authorized binaries are able to be executed. Due to a flaw in specific versions of Junos OS, affecting specific EX Series platforms, the Veriexec subsystem will fail to initialize, in essence disabling file integrity checking. This may allow a locally authenticated user with shell access to install untrusted executable images, and elevate privileges to gain full control of the system. During the installation of an affected version of Junos OS are installed, the following messages will be logged to the console: Initializing Verified Exec: /sbin/veriexec: Undefined symbol "__aeabi_uidiv" /sbin/veriexec: Undefined symbol "__aeabi_uidiv" /sbin/veriexec: Undefined symbol "__aeabi_uidiv" veriexec: /.mount/packages/db/os-kernel-prd-arm-32-20190221.70c2600_builder_stable_11/boot/brcm-hr3.dtb: Authentication error veriexec: /.mount/packages/db/os-kernel-prd-arm-32-20190221.70c2600_builder_stable_11/boot/contents.izo: Authentication error ... This issue affects Juniper Networks Junos OS: 18.1R3-S4 on EX2300, EX2300-C and EX3400; 18.3R1-S3 on EX2300, EX2300-C and EX3400.

Weakness: CWE-354 (Improper Validation of Integrity Check Value), CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2019-0071?

It affects 1 product.


Products: Juniper Junos.

## How do I fix CVE-2019-0071?

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

## Is CVE-2019-0071 being exploited?

There is no known exploitation of CVE-2019-0071 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-2019-0071 and fix it if it is affected.

What it is: CVE-2019-0071 is a high-severity vulnerability in Juniper Junos, published on 9 Oct 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-0071 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-2019-0071/ (Markdown: https://insights.sbomify.com/CVE-2019-0071/index.md)
```

## Sources

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

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