# CVE-2014-3345: Missing authorization in n/a

> Remote attackers can modify the Cisco Transport Gateway product via crafted URLs due to missing authorization checks on administrative web pages.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 28 Aug 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hmrc-p39f-mg22

## What is CVE-2014-3345?

CVE-2014-3345 is a medium-severity missing authorization vulnerability in n/a, published on 28 Aug 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The web framework in Cisco Transport Gateway for Smart Call Home (aka TG-SCH or Transport Gateway Installation Software) 4.0 does not properly check authorization for administrative web pages, which allows remote attackers to modify the product via a crafted URL, aka Bug ID CSCuq31503.

Weakness: CWE-264

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

It affects 1 product.


Products: Cisco Transport Gateway Installation Software.

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

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

## Is CVE-2014-3345 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-3346](https://insights.sbomify.com/CVE-2014-3346/): Denial of service in n/a (medium 6.3)
- [CVE-2016-6359](https://insights.sbomify.com/CVE-2016-6359/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2014-3344](https://insights.sbomify.com/CVE-2014-3344/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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