# CVE-2023-3349: Information exposure on IBERMATICA RPS

> Unauthenticated attackers can access a status page to enable logging and download log files containing sensitive data like usernames and SQL queries.

- **Severity:** High 8.2 (`CVSS:3.1/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:** 3 Oct 2023
- **Updated:** 19 Sep 2024
- **Also known as:** GHSA-cr9w-99vr-7f2h

## What is CVE-2023-3349?

CVE-2023-3349 is a high-severity vulnerability in IBERMATICA RPS 2019, published on 3 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Information exposure vulnerability in IBERMATICA RPS 2019, which exploitation could allow an unauthenticated user to retrieve sensitive information, such as usernames, IP addresses or SQL queries sent to the application. By accessing the URL /RPS2019Service/status.html, the application enables the logging mechanism by generating the log file, which can be downloaded.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Ayesa Ibermatica Rps.

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

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

## Is CVE-2023-3349 being exploited?

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

## Other vulnerabilities in IBERMATICA RPS 2019

- [CVE-2023-3350](https://insights.sbomify.com/CVE-2023-3350/): Cryptographic Issues on IBERMATICA RPS (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-3349 is a high-severity vulnerability in IBERMATICA RPS 2019, published on 3 Oct 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-3349 in the wild and no public exploit code.

Affected product: IBERMATICA RPS 2019. 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-3349/ (Markdown: https://insights.sbomify.com/CVE-2023-3349/index.md)
```

## Sources

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

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