# CVE-2023-1899: CVE-2023-1899

> An attacker can monitor network traffic to gain sensitive information because the web server does not use secure connections by default.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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:** 12 Jun 2023
- **Updated:** 6 Jan 2025
- **Also known as:** GHSA-rrmp-fhmw-8rh4

## What is CVE-2023-1899?

CVE-2023-1899 is a critical vulnerability in Atlas Copco Power Focus, published on 12 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Atlas Copco Power Focus 6000 web server is not a secure connection by default, which could allow an attacker to gain sensitive information by monitoring network traffic between user and controller.

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

It affects 1 product.


Products: Atlascopco Power Focus 6000 Firmware.

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

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

## Is CVE-2023-1899 being exploited?

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

## Other vulnerabilities in Atlas Copco Power Focus

- [CVE-2023-1897](https://insights.sbomify.com/CVE-2023-1897/): CVE-2023-1897 (critical 9.4)
- [CVE-2023-1898](https://insights.sbomify.com/CVE-2023-1898/): CVE-2023-1898 (critical 9.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-1899 is a critical vulnerability in Atlas Copco Power Focus, published on 12 Jun 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-1899 in the wild and no public exploit code.

Affected product: Atlas Copco Power Focus. 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-1899/ (Markdown: https://insights.sbomify.com/CVE-2023-1899/index.md)
```

## Sources

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

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