# CVE-2017-9625: Auth bypass in Envitech Ltd. EnviDAS Ultimate

> Attackers can bypass authentication to view information, modify settings, or execute code remotely in Envitech EnviDAS Ultimate.

- **Severity:** High 8.2 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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:** 17 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6ccc-wmjw-6qwc

## What is CVE-2017-9625?

CVE-2017-9625 is a high-severity authentication bypass vulnerability in Envitech Ltd. EnviDAS Ultimate, published on 17 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Improper Authentication issue was discovered in Envitech EnviDAS Ultimate Versions prior to v1.0.0.5. The web application lacks proper authentication which could allow an attacker to view information and modify settings or execute code remotely.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Envitech Envidas Ultimate.

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

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

## Is CVE-2017-9625 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9625 is a high-severity authentication bypass vulnerability in Envitech Ltd. EnviDAS Ultimate, published on 17 Oct 2017. 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-9625 in the wild and no public exploit code.

Affected product: Envitech Ltd. EnviDAS Ultimate. 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-9625/ (Markdown: https://insights.sbomify.com/CVE-2017-9625/index.md)
```

## Sources

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

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