# CVE-2017-6029: A Cross-Site Scripting issue was discovered in Certec EDV GmbH atvise scada prior to Version 3.0.


- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r3pc-gm9g-mm65

## What is CVE-2017-6029?

CVE-2017-6029 is a medium-severity vulnerability in Certec EDV GmbH atvise scada, published on 6 May 2017. 

### Official description

A Cross-Site Scripting issue was discovered in Certec EDV GmbH atvise scada prior to Version 3.0. This may allow remote code execution.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2017-6029?

It affects 1 product.


Products: Certec Edv Gmbh Atvise Scada.

## How do I fix CVE-2017-6029?

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

## Is CVE-2017-6029 being exploited?

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

## Other vulnerabilities in Certec EDV GmbH atvise scada

- [CVE-2017-6031](https://insights.sbomify.com/CVE-2017-6031/): Code injection in Certec EDV GmbH atvise scada (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6029 and fix it if it is affected.

What it is: CVE-2017-6029 is a medium-severity vulnerability in Certec EDV GmbH atvise scada, published on 6 May 2017. 
Exploitation: There is no known exploitation of CVE-2017-6029 in the wild and no public exploit code.

Affected product: Certec EDV GmbH atvise scada. 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-2017-6029/ (Markdown: https://insights.sbomify.com/CVE-2017-6029/index.md)
```

## Sources

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

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