# CVE-2019-1010308: Information disclosure in Aquarius CMS

> Attackers can access unrestricted log files containing sensitive data like passwords in Aquarius CMS.

- **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:** 15 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-g6px-r2w9-3w2v

## What is CVE-2019-1010308?

CVE-2019-1010308 is a critical vulnerability in Aquaverde GmbH Aquarius CMS, published on 15 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Aquaverde GmbH Aquarius CMS prior to version 4.1.1 is affected by: Incorrect Access Control. The impact is: The access to the log file is not restricted. It contains sensitive information like passwords etc. The component is: log file. The attack vector is: open the file.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2019-1010308?

It affects 1 product.


Products: Aquaverde Aquarius Cms.

## How do I fix CVE-2019-1010308?

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

## Is CVE-2019-1010308 being exploited?

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

## Other vulnerabilities in Aquaverde GmbH Aquarius CMS

- [CVE-2019-9724](https://insights.sbomify.com/CVE-2019-9724/): Information disclosure in n/a (high 7.5)
- [CVE-2019-9734](https://insights.sbomify.com/CVE-2019-9734/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1010308 and fix it if it is affected.

What it is: CVE-2019-1010308 is a critical vulnerability in Aquaverde GmbH Aquarius CMS, published on 15 Jul 2019. 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-2019-1010308 in the wild and no public exploit code.

Affected product: Aquaverde GmbH Aquarius CMS. 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-2019-1010308/ (Markdown: https://insights.sbomify.com/CVE-2019-1010308/index.md)
```

## Sources

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

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