Product
debian/lava vulnerabilities
10 published CVES affecting debian/lava, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 10
- Critical
- 1
- High
- 2
- Medium
- 3
- Low
- 0
- Unscored
- 4
- CISA KEV
- 0
Latest debian/lava CVEs
Newest publication first
-
Unknown
-
DSA-5318-1 lava - security update
PublishedUnknown -
CriticalCVSS 9.8 EPSS 2.1%
In Linaro Automated Validation Architecture (LAVA) before 2022.11.1, remote code execution can be achieved through user-submitted Jinja2 template. The REST API endpoint for validating device configuration files in lava-server loads input as a Jinja2 template in a way that can be...
-
MediumCVSS 6.5 EPSS 1.1%
In Linaro Automated Validation Architecture (LAVA) before 2022.11, users with valid credentials can submit crafted XMLRPC requests that cause a recursive XML entity expansion, leading to excessive use of memory on the server and a Denial of Service.
-
DLA-3192-1 lava - security update
PublishedUnknown -
DSA-5260-1 lava - security update
PublishedUnknown -
HighCVSS 8.8 EPSS 1.7%
In Linaro Automated Validation Architecture (LAVA) before 2022.10, there is dynamic code execution in lava_server/lavatable.py. Due to improper input sanitization, an anonymous user can force the lava-server-gunicorn service to execute user-provided code on the server.
-
HighCVSS 8.8 EPSS 2.4%
An issue was discovered in Linaro LAVA before 2018.5.post1. Because of use of yaml.load() instead of yaml.safe_load() when parsing user data, remote code execution can occur.
-
MediumCVSS 6.5 EPSS 1.5%
An issue was discovered in Linaro LAVA before 2018.5.post1. Because of support for URLs in the submit page, a user can forge an HTTP request that will force lava-server-gunicorn to return any file on the server that is readable by lavaserver and valid yaml.
-
MediumCVSS 6.5 EPSS 0.88%
An issue was discovered in Linaro LAVA before 2018.5.post1. Because of support for file: URLs, a user can force lava-server-gunicorn to download any file from the filesystem if it's readable by lavaserver and valid yaml.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.