# CVE-2024-41773: IBM Global Configuration Management incorrect ownership assignment

> An authenticated user can improperly archive a global baseline due to incorrect ownership assignment in IBM Global Configuration Management.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:** 20 Aug 2024
- **Updated:** 21 Aug 2024
- **Also known as:** GHSA-58qg-j84p-48jq

## What is CVE-2024-41773?

CVE-2024-41773 is a medium-severity missing authorization vulnerability in IBM Global Configuration Management, published on 20 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Global Configuration Management 7.0.2 and 7.0.3 could allow an authenticated user to archive a global baseline due to improper access controls.

Weakness: CWE-708 (Incorrect Ownership Assignment)

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

It affects 1 product.


Products: Ibm Global Configuration Management.

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

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

## Is CVE-2024-41773 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-41773 is a medium-severity missing authorization vulnerability in IBM Global Configuration Management, published on 20 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-41773 in the wild and no public exploit code.

Affected product: IBM Global Configuration Management. 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-41773/ (Markdown: https://insights.sbomify.com/CVE-2024-41773/index.md)
```

## Sources

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

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