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

> Remote attackers can access the MySQL database without authentication to read, modify data, or cause denial of service.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/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:** No
- **Published:** 24 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pjf5-76hq-mj8q

## What is CVE-2014-0674?

CVE-2014-0674 is a medium-severity authentication bypass vulnerability in n/a, published on 24 Jan 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco Video Surveillance Operations Manager (VSOM) does not require authentication for MySQL database connections, which allows remote attackers to obtain sensitive information, modify data, or cause a denial of service by leveraging network connectivity from a client system with a crafted host name, aka Bug ID CSCud10992.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Cisco Video Surveillance Operations Manager.

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

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

## Is CVE-2014-0674 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-3417](https://insights.sbomify.com/CVE-2013-3417/): Auth bypass in n/a (medium 5.0)
- [CVE-2013-3376](https://insights.sbomify.com/CVE-2013-3376/): Open redirect in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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