Skip to content
Fencer Intel
high 8.8

CVE-2021-40348 json

Spacewalk 2.10, and derivatives such as Uyuni 2021.08, allows code injection.

published 5y ago modified 4mo ago also EUVD-2021-27526

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 78%
public exploits
0
none known

Summary

Spacewalk 2.10, and derivatives such as Uyuni 2021.08, allows code injection. rhn-config-satellite.pl doesn't sanitize the configuration filename used to append Spacewalk-specific key-value pair. The script is intended to be run by the tomcat user account with Sudo, according to the installation setup. This can lead to the ability of an attacker to use --option to append arbitrary code to a root-owned file that eventually will be executed by the system. This is fixed in Uyuni spacewalk-admin 4.3.2-1.

Patch / fix

  • spacewalk-admin Manager Server Module 4.1 4.1.10-3.15.1
  • cobbler Manager Server Module 4.2 3.1.2-5.11.1
  • spacecmd Manager Server Module 4.2 4.2.13-4.9.1
  • susemanager Manager Server Module 4.2 4.2.25-3.13.1
  • spacewalk-web Manager Server Module 4.2 4.2.23-3.9.3
  • hub-xmlrpc-api Manager Server Module 4.2 0.7-3.3.3
  • spacewalk-java Manager Server Module 4.2 4.2.30-3.14.4
  • spacewalk-admin Manager Server Module 4.2 4.2.9-3.6.2

suse advisories SUSE-SU-2021:3562-1SUSE-SU-2021:3561-1SUSE-RU-2021:3551-1

Is CVE-2021-40348 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

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

Exploits and checks

  • openwall.com http://www.openwall.com/lists/oss-security/2021/10/28/4 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code

References

Sources

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.