# CVE-2024-42165: Arbitrary User Activation

> Attackers can predict activation tokens to arbitrarily activate user accounts in FIWARE Keyrock, leading to potential account takeover.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 12 Aug 2024
- **Updated:** 12 Aug 2024
- **Also known as:** GHSA-8h3p-v5fg-998p

## What is CVE-2024-42165?

CVE-2024-42165 is a medium-severity vulnerability in FIWARE Keyrock, published on 12 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Insufficiently random values for generating activation token in FIWARE Keyrock <= 8.4 allow attackers to activate accounts of any user by predicting the token for the activation link.

Weakness: CWE-330 (Use of Insufficiently Random Values)

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

It affects 1 product.


Products: Fiware Keyrock.

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

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

## Is CVE-2024-42165 being exploited?

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

## Other vulnerabilities in FIWARE Keyrock

- [CVE-2024-42166](https://insights.sbomify.com/CVE-2024-42166/): Command Injection in Applicationname (critical 9.1)
- [CVE-2024-42167](https://insights.sbomify.com/CVE-2024-42167/): Command Injection in Organisationname (critical 9.1)
- [CVE-2024-42163](https://insights.sbomify.com/CVE-2024-42163/): Password Manipulation (high 8.3)
- [CVE-2024-42164](https://insights.sbomify.com/CVE-2024-42164/): Disabling MFA without Authentication (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-42165 is a medium-severity vulnerability in FIWARE Keyrock, published on 12 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-42165 in the wild and no public exploit code.

Affected product: FIWARE Keyrock. 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-42165/ (Markdown: https://insights.sbomify.com/CVE-2024-42165/index.md)
```

## Sources

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

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