# CVE-2015-6254: Security feature bypass in n/a

> Attackers can bypass SAML destination validation in PicketLink, potentially allowing unauthorized access or assertion replay attacks.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Aug 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cc8r-2q55-6c87

## What is CVE-2015-6254?

CVE-2015-6254 is a medium-severity vulnerability in n/a, published on 17 Aug 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The (1) Service Provider (SP) and (2) Identity Provider (IdP) in PicketLink before 2.7.0 does not ensure that the Destination attribute in a Response element in a SAML assertion matches the location from which the message was received, which allows remote attackers to have unspecified impact via unknown vectors.  NOTE: this identifier was SPLIT from CVE-2015-0277 per ADT2 due to different vulnerability types.

Weakness: CWE-17

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

It affects 1 product.


Products: Picketlink Picketlink.

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

Upgrade to a fixed version.

## Is CVE-2015-6254 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-0277](https://insights.sbomify.com/CVE-2015-0277/): Auth bypass in n/a (medium 6.0)
- [CVE-2015-3158](https://insights.sbomify.com/CVE-2015-3158/): PicketLink does not properly check role based authorization (medium 4.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-6254 is a medium-severity vulnerability in n/a, published on 17 Aug 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-6254 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-2015-6254/ (Markdown: https://insights.sbomify.com/CVE-2015-6254/index.md)
```

## Sources

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

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