# CVE-2024-35451: Server-side request forgery in n/a

> An attacker can exploit a Server-Side Request Forgery vulnerability in LinkStack to access internal resources or bypass security controls.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Nov 2024
- **Updated:** 2 Dec 2024
- **Also known as:** GHSA-qmpq-m6m5-57hh

## What is CVE-2024-35451?

CVE-2024-35451 is a medium-severity server-side request forgery vulnerability in n/a, published on 29 Nov 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

LinkStack 2.7.9 through 4.7.7 allows resources\views\components\favicon.blade.php link SSRF.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Linkstack Linkstack.

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

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

## Is CVE-2024-35451 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-35451 exists.

## Other vulnerabilities in n/a

- [CVE-2023-5840](https://insights.sbomify.com/CVE-2023-5840/): Weak Password Recovery Mechanism for Forgotten Password in linkstackorg/linkstack (medium 6.5)
- [CVE-2023-5838](https://insights.sbomify.com/CVE-2023-5838/): Insufficient Session Expiration in linkstackorg/linkstack (medium 4.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-35451 is a medium-severity server-side request forgery vulnerability in n/a, published on 29 Nov 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-35451 exists.

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

## Sources

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

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