# CVE-2017-16852: Security feature bypass in n/a

> The Shibboleth Service Provider fails to verify metadata signatures and validity periods, allowing attackers to bypass critical security checks.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DLA-1179-1, DSA-4038-1, GHSA-5rhm-55rh-pvvp, SUSE-SU-2017:3215-1, UBUNTU-CVE-2017-16852

## What is CVE-2017-16852?

CVE-2017-16852 is a high-severity vulnerability in Debian Debian Linux, published on 16 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

shibsp/metadata/DynamicMetadataProvider.cpp in the Dynamic MetadataProvider plugin in Shibboleth Service Provider before 2.6.1 fails to properly configure itself with the MetadataFilter plugins and does not perform critical security checks such as signature verification, enforcement of validity periods, and other checks specific to deployments, aka SSPCPP-763.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `shibboleth-sp` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 2.5.5-6.3.1 |
| `shibboleth-sp` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 2.5.5-6.3.1 |
| `shibboleth-sp` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 2.5.5-6.3.1 |
| `shibboleth-sp` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 2.5.5-6.3.1 |
| `shibboleth-sp` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 2.5.5-6.3.1 |
| `shibboleth-sp` | SUSE:Linux Enterprise Software Development Kit 12 SP2 | All versions | 2.5.5-6.3.1 |
| `shibboleth-sp` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 2.5.5-6.3.1 |

Products: Debian Debian Linux, Shibboleth Service Provider.

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

Upgrade to a fixed version.

## Is CVE-2017-16852 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-16852 is a high-severity vulnerability in Debian Debian Linux, published on 16 Nov 2017. 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-2017-16852 in the wild and no public exploit code.

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

## Sources

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

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