CVE-2024-47179 Supply chain in RSSHub
Attackers can poison CI artifacts to execute arbitrary code and take over the repository via unvalidated file extraction in the Docker test workflow.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-47179?
CVE-2024-47179 is a high-severity vulnerability in DIYgod RSSHub, published on 26 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
RSSHub is an RSS network. Prior to commit 64e00e7, RSSHub's `docker-test-cont.yml` workflow is vulnerable to Artifact Poisoning, which could have lead to a full repository takeover. Downstream users of RSSHub are not vulnerable to this issue, and commit 64e00e7 fixed the underlying issue and made the repository no longer vulnerable. The `docker-test-cont.yml` workflow gets triggered when the `PR - Docker build test` workflow completes successfully. It then collects some information about the Pull Request that triggered the triggering workflow and set some labels depending on the PR body and sender. If the PR also contains a `routes` markdown block, it will set the `TEST_CONTINUE` environment variable to `true`. The workflow then downloads and extracts an artifact uploaded by the triggering workflow which is expected to contain a single `rsshub.tar.zst` file. However, prior to commit 64e00e7, it did not validate and the contents were extracted in the root of the workspace overriding any existing files. Since the contents of the artifact were not validated, it is possible for a malicious actor to send a Pull Request which uploads, not just the `rsshub.tar.zst` compressed docker image, but also a malicious `package.json` file with a script to run arbitrary code in the context of the privileged workflow. As of commit 64e00e7, this scenario has been addressed and the RSSHub repository is no longer vulnerable.
Weakness: CWE-20
Which versions are affected by CVE-2024-47179?
How do I fix CVE-2024-47179?
No fix has been published for CVE-2024-47179 yet. Limit exposure of the affected software until one is available.
Is CVE-2024-47179 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47179 exists.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-9mqc-fm24-h8cw.