# CVE-2014-7278: Denial of service in n/a

> Remote attackers can cause a persistent web-interface outage on ZyXEL Security Gateways by sending malicious JavaScript in login form data.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 4 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9r9m-5qr9-wxj8

## What is CVE-2014-7278?

CVE-2014-7278 is a medium-severity denial of service vulnerability in n/a, published on 4 Oct 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The login page on the ZyXEL SBG-3300 Security Gateway with firmware 1.00(AADY.4)C0 and earlier allows remote attackers to cause a denial of service (persistent web-interface outage) via JavaScript code within unspecified "welcome message" form data that is improperly handled during use for the loginMsg variable's value, a different vulnerability than CVE-2014-7277.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Zyxel Sbg3300-N, Zyxel Sbg3300-N Firmware.

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

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

## Is CVE-2014-7278 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-7277](https://insights.sbomify.com/CVE-2014-7277/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-7278 is a medium-severity denial of service vulnerability in n/a, published on 4 Oct 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-7278 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-7278/ (Markdown: https://insights.sbomify.com/CVE-2014-7278/index.md)
```

## Sources

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

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