# CVE-2011-0400: Security feature bypass in n/a

> Attackers can intercept session cookies over HTTP due to missing secure flags, potentially leading to account takeover.

- **Severity:** Medium 5.0 (`AV:N/AC:L/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:** No
- **Published:** 10 Jan 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2h8p-w5q4-c3jq

## What is CVE-2011-0400?

CVE-2011-0400 is a medium-severity vulnerability in n/a, published on 10 Jan 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cookie.php in Piwik before 1.1 does not set the secure flag for the session cookie in an https session, which makes it easier for remote attackers to capture this cookie by intercepting its transmission within an http session.

Weakness: CWE-16

## Which versions are affected by CVE-2011-0400?

It affects 1 product.


Products: Matomo Matomo.

## How do I fix CVE-2011-0400?

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

## Is CVE-2011-0400 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-7815](https://insights.sbomify.com/CVE-2015-7815/): Path traversal in n/a (high 7.5)
- [CVE-2015-7816](https://insights.sbomify.com/CVE-2015-7816/): Deserialization in n/a (high 7.5)
- [CVE-2009-4137](https://insights.sbomify.com/CVE-2009-4137/): Deserialization in n/a (high 7.5)
- [CVE-2009-4140](https://insights.sbomify.com/CVE-2009-4140/): File upload in n/a (high 7.5)
- [CVE-2011-4941](https://insights.sbomify.com/CVE-2011-4941/): Piwik (now Matomo) Vulnerable to Arbitrary Code Execution (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-0400 and fix it if it is affected.

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

## Sources

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

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