# CVE-2024-10863: Client-side audit exclusion vulnerability

> Attackers can manipulate client-side audit logs to exclude trails, compromising security monitoring in OpenText Secure Content Manager.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Nov 2024
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-95h2-5c4f-cpvp

## What is CVE-2024-10863?

CVE-2024-10863 is a medium-severity vulnerability in OpenText Secure Content Manager, published on 22 Nov 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

: Insufficient Logging vulnerability in OpenText Secure Content Manager on Windows allows Audit Log Manipulation.This issue affects Secure Content Manager: from 10.1 before <24.4.

End-users can potentially exploit the vulnerability to exclude audit trails from being recorded on the client side.

Weakness: CWE-778 (Insufficient Logging)

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


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

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

## Is CVE-2024-10863 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-10863 is a medium-severity vulnerability in OpenText Secure Content Manager, published on 22 Nov 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-10863 in the wild and no public exploit code.

Affected product: OpenText Secure Content Manager. 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-10863/ (Markdown: https://insights.sbomify.com/CVE-2024-10863/index.md)
```

## Sources

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

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