Docker image vulnerable to CVE-2025-55182

[mschenk]

I'm running two servers with Ozone from the docker images. Both got hit hard by the massive React2Shell vulnerability (CVE-2025-55182) over the weekend so I had to shut them down.

If you are running Ozone from Docker images, check your system for high CPU load and unknown processes now. The version or React in the image is vulnerable to remote code execution so your box may be part of a botnet or mining cryptocurrency right now.

[SteveTownsend]

wasn't this fixed in 0.1.99? Release notes do mention this CVE <img width="686" height="591" alt="Image" src="https://github.com/user-attachments/assets/37bf4b04-4aae-46b9-82ac-7fa7ea86a985" />

[mschenk]

wasn't this fixed in 0.1.99? Release notes do mention this CVE

It seems this only updates next.js. There still are references to the vulnerable react version (19.1.0) in package.json here: https://github.com/bluesky-social/ozone/pull/406/files

    "hls.js": "^1.5.13",
    "kbar": "^0.1.0-beta.45",
    "lande": "^1.0.10",
    "next": "15.2.6",
    "react": "19.1.0",
    "react-dom": "19.1.0",
    "react-dropzone": "^14.3.5",

I'm by no means an expert on next and react or even Docker but after I updated my image and restarted my server yesterday I woke up to a cryptominer and what looks like a botnet on my test server:

1000      278956  278932  0 Dec08 ?        00:00:00 dumb-init -- node ./service
1000      279008  278956  0 Dec08 ?        00:00:48 node ./service
1000      833932  278956  0 06:01 ?        00:00:00 wveyeng
1000      833933  833932  0 06:01 ?        00:01:26 wveyeng
1000      833934  833932  1 06:01 ?        00:03:50 wveyeng
1000      833956  833932  0 06:01 ?        00:00:00 [wveyeng] <defunct>
1000      833959  278956 90 06:01 ?        02:58:53 /var/tmp/softirq -o 45.94.31.89:443 -u react -p 3cthDeQ5 --tls --randomx-1gb-pages --opencl --cuda -B

[mschenk]

Also see:
GHSA-fv66-9v8q-g76r

[SteveTownsend]

Thanks for the info. Hopefully this gets a fix very soon.

…

On Tue, Dec 9, 2025, 4:47 AM Maarten Schenk ***@***.***> wrote: *mschenk* left a comment (bluesky-social/ozone#409) <#409 (comment)> Also see: GHSA-fv66-9v8q-g76r <https://github.com/facebook/react/security/advisories/GHSA-fv66-9v8q-g76r> — Reply to this email directly, view it on GitHub <#409 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADRDNC6URTPXC4VDD7UOATD4A2LCDAVCNFSM6AAAAACOMG6OGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMZRGMYDAOJZG4> . You are receiving this because you commented.Message ID: ***@***.***>

[mschenk]

~# ps -Af | grep 1000
1000 218052 218016 0 21:15 ? 00:00:00 dumb-init -- node ./service
1000 218074 218052 0 21:15 ? 00:00:04 node ./service
1000 222825 218052 0 21:21 ? 00:00:01 dockerd
1000 222851 222825 0 21:21 ? 00:00:00 dockerd
1000 222852 222825 0 21:21 ? 00:00:00 dockerd
1000 222883 222825 90 21:21 ? 00:03:32 /var/tmp/dockerd-daemon

Now it seems they are predending to be docker....? Notice the /var/tmp/ location...

[surfdude29]

Pinging @estrattonbailey @foysalit for visibility

[SteveTownsend]

Commit is great but it's not much use unless a release is made that includes the change.
This is a zero day vulnerability. It's inexcusable to be working on other commits while this is unpatched.

[foysalit]

Commit is great but it's not much use unless a release is made that includes the change. This is a zero day vulnerability. It's inexcusable to be working on other commits while this is unpatched.

hey @SteveTownsend I did send out the release after merging that PR. the new tag https://github.com/bluesky-social/ozone/releases/tag/v0.1.101 should trigger watchtower to pull the new image if you're running docker. I guess I could create a release entry but that is not required for watchtower to upgrade to the new image.

[SteveTownsend]

Ah ok. It was not showing in the Releases page until two hours ago. Thanks.

…

On Thu, Dec 11, 2025, 7:07 AM Foysal Ahamed ***@***.***> wrote: *foysalit* left a comment (bluesky-social/ozone#409) <#409 (comment)> Commit is great but it's not much use unless a release is made that includes the change. This is a zero day vulnerability. It's inexcusable to be working on other commits while this is unpatched. hey @SteveTownsend <https://github.com/SteveTownsend> I did send out the release after merging that PR. the new tag https://github.com/bluesky-social/ozone/releases/tag/v0.1.101 should trigger watchtower to pull the new image if you're running docker. I guess I could create a release entry but that is not required for watchtower to upgrade to the new image. — Reply to this email directly, view it on GitHub <#409 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADRDNC6OUXXQX423SWOYFQL4BFNAJAVCNFSM6AAAAACOMG6OGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNBRGYYTKOJUG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mschenk]

I spent some more time digging and it looks like my Ozone installation wasn't automatically updating like the installation instructions led me to believe would happen, and the instructions to manually update it (which I ran several times after the zero-day thing happened) apparently do not actually update the container image that is actually used when the ozone service starts if you follow the installation instructions.

The instructions at https://github.com/bluesky-social/ozone/blob/main/HOSTING.md said to run this for a manual update:

sudo docker pull ghcr.io/bluesky-social/ozone:latest

while the compose.yaml it tells you to download during installation from https://raw.githubusercontent.com/bluesky-social/ozone/main/service/compose.yaml says

 image: ghcr.io/bluesky-social/ozone:0.1

When I manually ran that docker pull command for that 0.1 version an actual update did happen. I.e.

sudo docker pull ghcr.io/bluesky-social/ozone:0.1

I restarted ozone and it has been running for several hours now without suspicious cryptominers etc. starting up.

I don't know if there are many other Ozone users with potentially the same issue but it might be worth adding a note to the documentation? All of this might be obvious to experienced docker users but it definitely tripped me up and had me running a version with a very serious security vulnerability for far too long...