# CVE-2014-3823: Cross-site scripting in n/a

> Remote attackers can perform clickjacking attacks on Juniper SSL VPN devices, requiring user interaction to bypass security controls.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Sep 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-x6pp-j24v-837c

## What is CVE-2014-3823?

CVE-2014-3823 is a medium-severity cross-site scripting vulnerability in n/a, published on 29 Sep 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Juniper Junos Pulse Secure Access Service (SSL VPN) devices with IVE OS 8.0 before 8.0r1, 7.4 before 7.4r5, and 7.1 before 7.1r18 allows remote attackers to conduct clickjacking attacks via unspecified vectors.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Juniper Junos Pulse Secure Access Service.

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

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

## Is CVE-2014-3823 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-3824](https://insights.sbomify.com/CVE-2014-3824/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-3823 is a medium-severity cross-site scripting vulnerability in n/a, published on 29 Sep 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-3823 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-2014-3823/ (Markdown: https://insights.sbomify.com/CVE-2014-3823/index.md)
```

## Sources

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

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