# CVE-2015-4171: Information disclosure in n/a

> Remote attackers can obtain credentials by exploiting a flaw in strongSwan's IKEv2 authentication process when using EAP or pre-shared keys.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jun 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-4171, DLA-244-1, DSA-3282-1, GHSA-mg6m-fcfp-8xqm, SUSE-SU-2015:1196-1, SUSE-SU-2015:1791-1, UBUNTU-CVE-2015-4171, USN-2628-1

## What is CVE-2015-4171?

CVE-2015-4171 is a low-severity vulnerability in Canonical Ubuntu Linux, published on 10 Jun 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

strongSwan 4.3.0 through 5.x before 5.3.2 and strongSwan VPN Client before 1.4.6, when using EAP or pre-shared keys for authenticating an IKEv2 connection, does not enforce server authentication restrictions until the entire authentication process is complete, which allows remote servers to obtain credentials by using a valid certificate and then reading the responses.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2015-4171?

It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `strongswan` | SUSE:Linux Enterprise Desktop 12 | All versions | 5.1.3-18.1 |
| `strongswan` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 4.4.0-6.29.2 |
| `strongswan` | SUSE:Linux Enterprise Server 12 | All versions | 5.1.3-18.1 |
| `strongswan` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 4.4.0-6.29.2 |
| `strongswan` | SUSE:Linux Enterprise Server for SAP Applications 12 | All versions | 5.1.3-18.1 |

Products: Canonical Ubuntu Linux, Debian Debian Linux, Strongswan Strongswan, Strongswan Strongswan Vpn Client.

## How do I fix CVE-2015-4171?

Upgrade to a fixed version.

## Is CVE-2015-4171 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-4171 and fix it if it is affected.

What it is: CVE-2015-4171 is a low-severity vulnerability in Canonical Ubuntu Linux, published on 10 Jun 2015. 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-2015-4171 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. 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-2015-4171/ (Markdown: https://insights.sbomify.com/CVE-2015-4171/index.md)
```

## Sources

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

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