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

> Remote attackers can steal sensitive session cookies from the PCS daemon due to missing HTTPOnly flags, potentially leading to session hijacking.

- **Severity:** Medium 4.3 (`AV:N/AC:M/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:** 14 May 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vp3g-8qhm-pw5j

## What is CVE-2015-3983?

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

### Official description

The pcs daemon (pcsd) in PCS 0.9.137 and earlier does not include the HTTPOnly flag in a Set-Cookie header, which makes it easier for remote attackers to obtain potentially sensitive information via script access to this cookie.  NOTE: this issue was SPLIT from CVE-2015-1848 per ADT2 due to different vulnerability types.

Weakness: CWE-310

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

It affects 1 product.


Products: Fedora Pacemaker Configuration System.

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

Upgrade to a fixed version.

## Is CVE-2015-3983 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-1848](https://insights.sbomify.com/CVE-2015-1848/): Information disclosure in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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