# CVE-2024-12123: Unauthorized Modification of Ticket Requester

> Authenticated users can modify hidden fields to change the ticket requester, allowing unauthorized modification of ticket ownership.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/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:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2024
- **Updated:** 4 Dec 2024
- **Also known as:** GHSA-2jgc-wx9f-vpp5

## What is CVE-2024-12123?

CVE-2024-12123 is a medium-severity vulnerability in Issuetrak, published on 4 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A hidden field manipulation vulnerability was identified in Issuetrak version 17.1 that could be triggered by an authenticated user. 

When an authenticated user submits a ticket, the request can be intercepted and subsequently modified by using a proxy.  The ticket requester can be changed from the original requester to another user in the same application, 
which the application then accepts.

Weakness: CWE-837 (Improper Enforcement of a Single, Unique Action), CWE-472 (External Control of Assumed-Immutable Web Parameter)

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


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

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

## Is CVE-2024-12123 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-12123 is a medium-severity vulnerability in Issuetrak, published on 4 Dec 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-12123 in the wild and no public exploit code.

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

## Sources

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

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