# CVE-2024-23568: Information disclosure in Aftermarket EPC

> The web server reveals software version information, allowing attackers to identify potential vulnerabilities in the HCL Aftermarket EPC application.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-34jp-jwp8-9p5j

## What is CVE-2024-23568?

CVE-2024-23568 is a medium-severity vulnerability in HCLSoftware Aftermarket EPC, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HCL Aftermarket EPC is vulnerable to attacks since the server software version used by the application is revealed by the web server. Displaying version information of software could allow an attacker to determine which vulnerabilities are present in the software, particularly if an outdated software version is in use with published vulnerabilities.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2024-23568 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-23568 is a medium-severity vulnerability in HCLSoftware Aftermarket EPC, published on 17 Jul 2026. 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-2024-23568 in the wild and no public exploit code.

Affected product: HCLSoftware Aftermarket EPC. 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-23568/ (Markdown: https://insights.sbomify.com/CVE-2024-23568/index.md)
```

## Sources

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

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