# CVE-2019-9724: Information disclosure in n/a

> Attackers can access sensitive information stored in log files due to a flaw in the Aquarius CMS log writer.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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:** 24 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2ghv-58hc-7529

## What is CVE-2019-9724?

CVE-2019-9724 is a high-severity vulnerability in n/a, published on 24 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

aquaverde Aquarius CMS through 4.3.5 allows Information Exposure through Log Files because of an error in the Log-File writer component.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

It affects 1 product.


Products: Aquaverde Aquarius Cms.

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

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

## Is CVE-2019-9724 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-1010308](https://insights.sbomify.com/CVE-2019-1010308/): Information disclosure in Aquarius CMS (critical 9.8)
- [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-9724 and fix it if it is affected.

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

## Sources

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

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