# CVE-2017-7411: Deserialization in n/a

> Attackers can achieve remote code execution in Tuleap by injecting malicious PHP objects via the REST API due to unsafe deserialization.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-f58h-hjj3-8549

## What is CVE-2017-7411?

CVE-2017-7411 is a high-severity unsafe deserialization vulnerability in Enalean Tuleap, published on 30 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Enalean Tuleap 9.6 and prior versions. The vulnerability exists because the User::getRecentElements() method is using the unserialize() function with a preference value that can be arbitrarily manipulated by malicious users through the REST API interface, and this can be exploited to inject arbitrary PHP objects into the application scope, allowing an attacker to perform a variety of attacks (including but not limited to Remote Code Execution).

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2017-7411?

It affects 1 product.


Products: Enalean Tuleap.

## How do I fix CVE-2017-7411?

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

## Is CVE-2017-7411 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-7411 exists.

Public exploit code:

- Tuleap 9.6 Second-Order PHP Object Injection (metasploit)
- Tuleap 9.6 - Second-Order PHP Object Injection (Metasploit) (exploitdb)
- Tuleap 9.6 - Second-Order PHP Object Injection (Metasploit) (exploitdb)

## Other vulnerabilities in Enalean Tuleap

- [CVE-2018-17298](https://insights.sbomify.com/CVE-2018-17298/): Business logic in n/a (critical 9.8)
- [CVE-2018-7538](https://insights.sbomify.com/CVE-2018-7538/): SQL injection in n/a (critical 9.8)
- [CVE-2014-7178](https://insights.sbomify.com/CVE-2014-7178/): Command injection in n/a (critical 9.3)
- [CVE-2021-43806](https://insights.sbomify.com/CVE-2021-43806/): SQL injection in Tuleap (high 8.8)
- [CVE-2021-41154](https://insights.sbomify.com/CVE-2021-41154/): SQL injection in the "SVN core" commits browser (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-7411 and fix it if it is affected.

What it is: CVE-2017-7411 is a high-severity unsafe deserialization vulnerability in Enalean Tuleap, published on 30 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-7411 exists.

Affected product: Enalean Tuleap. 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-2017-7411/ (Markdown: https://insights.sbomify.com/CVE-2017-7411/index.md)
```

## Sources

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

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