# CVE-2022-1561: Crafted backend URLs in Lura Project

> Attackers can manipulate backend URLs in Lura Project and KrakenD, potentially accessing internal services or bypassing security controls.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-mj97-cwp5-r4v9

## What is CVE-2022-1561?

CVE-2022-1561 is a medium-severity server-side request forgery vulnerability in KrakenD-CE, published on 1 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Lura and KrakenD-CE versions older than v2.0.2 and KrakenD-EE versions older than v2.0.0 do not sanitize URL parameters correctly, allowing a malicious user to alter the backend URL defined for a pipe when remote users send crafty URL requests. The vulnerability does not affect KrakenD itself, but the consumed backend might be vulnerable.

Weakness: CWE-471 (Modification of Assumed-Immutable Data (MAID))

## Which versions are affected by CVE-2022-1561?

It affects 2 products.


Products: Krakend Krakend, Luraproject Lura.

## How do I fix CVE-2022-1561?

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

## Is CVE-2022-1561 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1561 and fix it if it is affected.

What it is: CVE-2022-1561 is a medium-severity server-side request forgery vulnerability in KrakenD-CE, published on 1 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1561 in the wild and no public exploit code.

Affected product: KrakenD-CE. 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-2022-1561/ (Markdown: https://insights.sbomify.com/CVE-2022-1561/index.md)
```

## Sources

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

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