# CVE-2014-3274: Security feature bypass in n/a

> Man-in-the-middle attackers can intercept sensitive directory information by forcing HTTP fallback when HTTPS fails in Cisco TelePresence Systems.

- **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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5r36-q7mm-42xf

## What is CVE-2014-3274?

CVE-2014-3274 is a medium-severity vulnerability in n/a, published on 23 May 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Cisco TelePresence System (CTS) 6.0(.5)(5) and earlier falls back to HTTP when certain HTTPS sessions cannot be established, which allows man-in-the-middle attackers to obtain sensitive directory information by leveraging a network position between CTS and Cisco Unified Communications Manager (UCM) to block HTTPS traffic, aka Bug ID CSCuj26326.

Weakness: CWE-310

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

It affects 1 product.


Products: Cisco Telepresence System Software.

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

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

## Is CVE-2014-3274 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-0330](https://insights.sbomify.com/CVE-2012-0330/): Denial of service in n/a (high 7.8)
- [CVE-2012-0331](https://insights.sbomify.com/CVE-2012-0331/): Denial of service in n/a (high 7.5)
- [CVE-2013-1246](https://insights.sbomify.com/CVE-2013-1246/): Denial of service in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-3274 is a medium-severity vulnerability in n/a, published on 23 May 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-3274 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-3274/ (Markdown: https://insights.sbomify.com/CVE-2014-3274/index.md)
```

## Sources

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

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