# CVE-2014-6304: Information disclosure in n/a

> Remote attackers can obtain sensitive source-code information from the Form Controls CSS file in PNMsoft Sequence Kinetics.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 19 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wwgr-p7g6-6h59

## What is CVE-2014-6304?

CVE-2014-6304 is a medium-severity vulnerability in n/a, published on 19 Feb 2015. It can be exploited over the network.

### Official description

The Form Controls CSS file in PNMsoft Sequence Kinetics before 7.7 allows remote attackers to obtain sensitive source-code information via unspecified vectors.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Pnmsoft Sequence Kinetics.

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

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

## Is CVE-2014-6304 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-6302](https://insights.sbomify.com/CVE-2014-6302/): XML external entity in n/a (medium 5.0)
- [CVE-2014-6303](https://insights.sbomify.com/CVE-2014-6303/): XML external entity in n/a (medium 5.0)
- [CVE-2014-6301](https://insights.sbomify.com/CVE-2014-6301/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-6304 is a medium-severity vulnerability in n/a, published on 19 Feb 2015. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2014-6304 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-6304/ (Markdown: https://insights.sbomify.com/CVE-2014-6304/index.md)
```

## Sources

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

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