# CVE-2014-2950: Auth bypass in n/a

> Remote attackers can access sensitive information via FTP without authentication on Datum Systems SnIP devices.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/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:** 14 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6gjr-pq9v-gx94

## What is CVE-2014-2950?

CVE-2014-2950 is a high-severity authentication bypass vulnerability in n/a, published on 14 Jul 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Datum Systems SnIP on PSM-500 and PSM-4500 devices does not require authentication for FTP sessions, which allows remote attackers to obtain sensitive information via RETR commands.

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

It affects 1 product.


Products: Datumsystems Snip.

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

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

## Is CVE-2014-2950 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-2951](https://insights.sbomify.com/CVE-2014-2951/): Hardcoded credentials in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2950 is a high-severity authentication bypass vulnerability in n/a, published on 14 Jul 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-2950 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-2950/ (Markdown: https://insights.sbomify.com/CVE-2014-2950/index.md)
```

## Sources

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

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