# CVE-2023-51708: Information disclosure in n/a

> Unauthenticated attackers can view configuration options in Bentley Assetwise Integrity Information Server via crafted requests, exposing sensitive system settings.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/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:** 22 Dec 2023
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-xgc4-wqm7-7qrj

## What is CVE-2023-51708?

CVE-2023-51708 is a high-severity vulnerability in n/a, published on 22 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Bentley eB System Management Console applications within Assetwise Integrity Information Server allow an unauthenticated user to view configuration options via a crafted request, leading to information disclosure. This affects eB System management Console before 23.00.02.03 and Assetwise ALIM For Transportation before 23.00.01.25.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2023-51708?

It affects 2 products.


Products: Bentley Assetwise Alim for Transportation, Bentley Eb System Management Console.

## How do I fix CVE-2023-51708?

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

## Is CVE-2023-51708 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-51708 and fix it if it is affected.

What it is: CVE-2023-51708 is a high-severity vulnerability in n/a, published on 22 Dec 2023. 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-2023-51708 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-2023-51708/ (Markdown: https://insights.sbomify.com/CVE-2023-51708/index.md)
```

## Sources

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

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