Crafted backend URLs in Lura Project

published 2022-08-01 4y ago modified 2026-06-17 4mo ago also EUVD-2022-24853

cvss: 4.0; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 48%
public exploits: 0; none known

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.

Patch / fix

fixed in 2

krakend krakend 2.0.0
luraproject lura 2.0.2

Is CVE-2022-1561 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	4.0	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N
NVD	3.1	4.3	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected products

KrakenD Lura Project
KrakenD KrakenD-CE
KrakenD KrakenD-EE

Classification

Weakness

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

References

krakend.io /blog/cve-2022-1561-crafted-backend-urls/
vendor-advisory
incibe-cert.es /en/early-warning/security-advisories/crafted-backend-urls-lura-project
third-party-advisory

Sources

CVE List CVE-2022-1561
NVD CVE-2022-1561

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.