github bbernhard/signal-cli-rest-api 0.102
Version 0.102

one hour ago

Important Security Fixes

  • updated OpenJDK to v25.0.5.1, which contains a fix for the Java4Shell vulnerability; the native image is still built with GraalVM 25.0.x and shouldn't be vulnerable to Java4Shell

  • fixed path traversal vulnerability: When sending a message with an attachment, the attachment is first written to a temporary directory inside the container (this is needed, as signal-cli only operates on attachment files). Due to a missing check a maliciously crafted base64_attachments argument can be used to break out of this temporary directory and overwrite any file mounted into the container.

If the sample configuration (as described in the README.md) is used, the only folder that gets mounted into the container is the one with the signal-cli config. That means, the worst thing that can happen, is that the the contents of the signal-cli config gets overwritten, which results in a broken setup and requires a new registration with the Signal Service. It is not possible to read out any private signal-cli config that way!

Credits go to @mafredri who found this issue and reached out to me in private to notify me about it. Thanks a lot - very much appreciated!

(There will also be a security advisory published as soon as Github has assigned the CVE)

Bug Fixes + New Features

  • updated signal-cli to v0.14.10
  • fixed path traversal vulnerability (see above for details) - thanks to @mafredri
  • add a new endpoint to terminate a group for everyone (thanks to @jgiambo)
  • added numberless support (thanks to @jasonmccuen)
  • added the possibility to set the receive mode (via the JSON_RPC_RECEIVE_MODE env variable) to manual to prevent message loss in certain circumstances in the json-rpc mode (thanks to @MykolaBalakin)
  • fixed a few wrong annotations in the swagger documentation (thanks to @Gara-Dorta)
  • atomically write jsonrpc2.yml file, which fixes a race that can occur when the signal-cli config folder is stored on a slow (network) storage
  • redirect stdout output to /dev/null to avoid spamming the docker log in the json-rpc mode when one or multiple websocket clients are connected
  • properly set --output=json when starting signal-cli in json-rpc mode (this was a regression when moving from supervisorctl to s6)

Don't miss a new signal-cli-rest-api release

NewReleases is sending notifications on new releases.