# CVE-2014-2212: Information disclosure in n/a

> Attackers can steal credentials by reading cookies containing cleartext usernames and MD5 password hashes from the POSH portal remember me feature.

- **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:** 1 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2vq9-q9w6-2hh6

## What is CVE-2014-2212?

CVE-2014-2212 is a medium-severity vulnerability in n/a, published on 1 Apr 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The remember me feature in portal/scr_authentif.php in POSH (aka Posh portal or Portaneo) 3.0, 3.2.1, 3.3.0, and earlier stores the username and MD5 digest of the password in cleartext in a cookie, which allows attackers to obtain sensitive information by reading this cookie.

Weakness: CWE-255

## Which versions are affected by CVE-2014-2212?

It affects 1 product.


Products: Posh Project Posh.

## How do I fix CVE-2014-2212?

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

## Is CVE-2014-2212 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-2211](https://insights.sbomify.com/CVE-2014-2211/): SQL injection in n/a (high 7.5)
- [CVE-2014-2213](https://insights.sbomify.com/CVE-2014-2213/): Open redirect in n/a (medium 6.1)
- [CVE-2014-2214](https://insights.sbomify.com/CVE-2014-2214/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2212 and fix it if it is affected.

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

## Sources

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

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