# CVE-2025-22828: Apache CloudStack: Unauthorised access to annotations

> Authenticated users can read or add annotations to resources without proper authorization if they know the resource UUIDs.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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:** 13 Jan 2025
- **Updated:** 13 Jan 2025
- **Also known as:** GHSA-7jhp-8mw7-9mrw

## What is CVE-2025-22828?

CVE-2025-22828 is a medium-severity missing authorization vulnerability in Apache Cloudstack, published on 13 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

CloudStack users can add and read comments (annotations) on resources they are authorised to access. 

Due to an access validation issue that affects Apache CloudStack versions from 4.16.0, users who have access, prior access or knowledge of resource UUIDs can list and add comments (annotations) to such resources. 

An attacker with a user-account and access or prior knowledge of resource UUIDs may exploit this issue to read contents of the comments (annotations) or add malicious comments (annotations) to such resources. 

This may cause potential loss of confidentiality of CloudStack environments and resources if the comments (annotations) contain any privileged information. However, guessing or brute-forcing resource UUIDs are generally hard to impossible and access to listing or adding comments isn't same as access to CloudStack resources, making this issue of very low severity and general low impact.

CloudStack admins may also disallow listAnnotations and addAnnotation API access to non-admin roles in their environment as an interim measure.

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

## Which versions are affected by CVE-2025-22828?

It affects 1 product.


Products: Apache Cloudstack.

## How do I fix CVE-2025-22828?

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

## Is CVE-2025-22828 being exploited?

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

Public exploit code:

- Apache CloudStack vulnerability allows unauthorized access to annotations on certain resources. (github_poc): https://github.com/Stolichnayer/CVE-2025-22828

## Other vulnerabilities in Apache Cloudstack

- [CVE-2012-4501](https://insights.sbomify.com/CVE-2012-4501/): Missing authorization in n/a (critical 10.0)
- [CVE-2024-38346](https://insights.sbomify.com/CVE-2024-38346/): Apache CloudStack: Unauthenticated cluster service port leads to remote execution (critical 9.8)
- [CVE-2024-39864](https://insights.sbomify.com/CVE-2024-39864/): Apache CloudStack: Integration API service uses dynamic port when disabled (critical 9.8)
- [CVE-2024-29006](https://insights.sbomify.com/CVE-2024-29006/): Apache CloudStack: x-forwarded-for HTTP header parsed by default (critical 9.8)
- [CVE-2022-35741](https://insights.sbomify.com/CVE-2022-35741/): Apache CloudStack SAML Single Sign-On XXE (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-22828 and fix it if it is affected.

What it is: CVE-2025-22828 is a medium-severity missing authorization vulnerability in Apache Cloudstack, published on 13 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-22828 in the wild and no public exploit code.

Affected product: Apache Cloudstack. 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-2025-22828/ (Markdown: https://insights.sbomify.com/CVE-2025-22828/index.md)
```

## Sources

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

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