# CVE-2024-28113: Open redirection using the return_url parameter in Peering Manager


- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 12 Mar 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-f4mf-5g28-q7f5

## What is CVE-2024-28113?

CVE-2024-28113 is a low-severity vulnerability in peering-manager, published on 12 Mar 2024. 

### Official description

Peering Manager is a BGP session management tool. In Peering Manager <=1.8.2, it is possible to redirect users to an arbitrary page using a crafted url. As a result users can be redirected to an unexpected location. This issue has been addressed in version 1.8.3. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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

It affects 1 product.


Products: Peering-Manager Peering Manager.

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

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

## Is CVE-2024-28113 being exploited?

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

## Other vulnerabilities in peering-manager

- [CVE-2024-28114](https://insights.sbomify.com/CVE-2024-28114/): Remote Code Execution using Server Side Template Injection in Peering Manager (high 8.1)
- [CVE-2024-28112](https://insights.sbomify.com/CVE-2024-28112/): Cross site scripting on router page in Peering Manager (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28113 is a low-severity vulnerability in peering-manager, published on 12 Mar 2024. 
Exploitation: There is no known exploitation of CVE-2024-28113 in the wild and no public exploit code.

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

## Sources

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

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