# CVE-2016-4334: Open redirect in Jive before 2016.3.1

> An attacker can redirect users to malicious sites via the external-link.jspa page in Jive, potentially facilitating phishing attacks.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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:** 10 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-44pf-4r67-pwjx

## What is CVE-2016-4334?

CVE-2016-4334 is a medium-severity vulnerability in Jive before 2016.3.1, published on 10 Apr 2017. 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

Jive before 2016.3.1 has an open redirect from the external-link.jspa page.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2016-4334?

It affects 1 product.


Products: Jivesoftware Jive.

## How do I fix CVE-2016-4334?

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

## Is CVE-2016-4334 being exploited?

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

## Other vulnerabilities in Jive before 2016.3.1

- [CVE-2021-45968](https://insights.sbomify.com/CVE-2021-45968/): Server-side request forgery in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-4334 and fix it if it is affected.

What it is: CVE-2016-4334 is a medium-severity vulnerability in Jive before 2016.3.1, published on 10 Apr 2017. 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-2016-4334 in the wild and no public exploit code.

Affected product: Jive before 2016.3.1. 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-2016-4334/ (Markdown: https://insights.sbomify.com/CVE-2016-4334/index.md)
```

## Sources

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

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