# CVE-2024-11923: Sensitive Information Disclosure in Fortra Application Hub Prior to version 1.3

> Attackers can read sensitive credentials from log files in Fortra Application Hub when specific logging settings are enabled.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jan 2025
- **Updated:** 22 Jan 2025
- **Also known as:** GHSA-hq9p-3gpg-pgpq

## What is CVE-2024-11923?

CVE-2024-11923 is a medium-severity vulnerability in Fortra Application Hub, published on 17 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Under certain log settings the IAM or CORE service will log credentials in the iam logfile in Fortra Application Hub (Formerly named Helpsystems One) prior to version 1.3

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

## Which versions are affected by CVE-2024-11923?


## How do I fix CVE-2024-11923?

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

## Is CVE-2024-11923 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-11923 and fix it if it is affected.

What it is: CVE-2024-11923 is a medium-severity vulnerability in Fortra Application Hub, published on 17 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-11923 in the wild and no public exploit code.

Affected product: Fortra Application Hub. 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-2024-11923/ (Markdown: https://insights.sbomify.com/CVE-2024-11923/index.md)
```

## Sources

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

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