# CVE-2017-17974: Information disclosure in n/a

> Remote attackers can obtain sensitive administrative credentials via specific web requests, leading to unauthorized access on BAS Web devices.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Dec 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-mwhh-pvh6-rh64

## What is CVE-2017-17974?

CVE-2017-17974 is a critical vulnerability in n/a, published on 29 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

BA SYSTEMS BAS Web on BAS920 devices (with Firmware 01.01.00*, HTTPserv 00002, and Script 02.*) and ISC2000 devices allows remote attackers to obtain sensitive information via a request for isc/get_sid_js.aspx or isc/get_sid.aspx, as demonstrated by obtaining administrative access by subsequently using the credential information for the Supervisor/Administrator account.

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

It affects 2 products.


Products: Basystems Bas920 Firmware, Basystems Isc2000 Firmware.

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

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

## Is CVE-2017-17974 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17974 is a critical vulnerability in n/a, published on 29 Dec 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-17974 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-2017-17974/ (Markdown: https://insights.sbomify.com/CVE-2017-17974/index.md)
```

## Sources

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

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