# CVE-2017-20007: Information Exposure in INGEPAC DA AU

> Unauthenticated attackers can access sensitive configuration files via the web interface, potentially aiding further attacks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 25 Oct 2021
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4hm5-q7h9-438p

## What is CVE-2017-20007?

CVE-2017-20007 is a medium-severity vulnerability in Ingeteam INGEPAC DA AU, published on 25 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ingeteam INGEPAC DA AU AUC_1.13.0.28 (and before) web application allows access to a certain path that contains sensitive information that could be used by an attacker to execute more sophisticated attacks. An unauthenticated remote attacker with access to the device´s web service could exploit this vulnerability in order to obtain different configuration files.

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

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

It affects 1 product.


Products: Ingeteam Ingepac Da Au Firmware.

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

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

## Is CVE-2017-20007 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-20007 is a medium-severity vulnerability in Ingeteam INGEPAC DA AU, published on 25 Oct 2021. 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-2017-20007 in the wild and no public exploit code.

Affected product: Ingeteam INGEPAC DA AU. 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-20007/ (Markdown: https://insights.sbomify.com/CVE-2017-20007/index.md)
```

## Sources

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

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