# CVE-2023-28953: IBM Cognos Analytics on Cloud Pak for Data improper access control

> Attackers can compromise container security via system calls due to misconfigured security contexts in IBM Cognos Analytics on Cloud Pak for Data.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2023
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-h2j9-wrpc-7mm8

## What is CVE-2023-28953?

CVE-2023-28953 is a low-severity vulnerability in IBM Cognos Analytics Cartridge for Cloud Pak for Data, published on 10 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Cognos Analytics on Cloud Pak for Data 4.0 could allow an attacker to make system calls that might compromise the security of the containers due to misconfigured security context.  IBM X-Force ID:  251465.

## Which versions are affected by CVE-2023-28953?

It affects 1 product.


Products: Ibm Cognos Analytics Cartridge for Ibm Cloud Pak for Data.

## How do I fix CVE-2023-28953?

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

## Is CVE-2023-28953 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-28953 and fix it if it is affected.

What it is: CVE-2023-28953 is a low-severity vulnerability in IBM Cognos Analytics Cartridge for Cloud Pak for Data, published on 10 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-28953 in the wild and no public exploit code.

Affected product: IBM Cognos Analytics Cartridge for Cloud Pak for Data. 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-2023-28953/ (Markdown: https://insights.sbomify.com/CVE-2023-28953/index.md)
```

## Sources

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

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