First published: Fri Aug 02 2024(Updated: )
Even with `authorized_keys` is filled with allowed pubkeys, If `noscraper` is enabled, It will allow anyone to use bouncer even it's pubkey is not in `authorized_keys`. ### Impact - Private bouncer ### Patches Available on version [3.0.10](https://github.com/Yonle/bostr/releases/tag/3.0.10) ### Workarounds Disable `noscraper` if you have `authorized_keys` being set in config ### References This [line of code](https://github.com/Yonle/bostr/blob/8665374a66e2afb9f92d0414b0d6f420a95d5d2d/auth.js#L21) is the cause.
Affected Software | Affected Version | How to fix |
---|---|---|
npm/bostr | <3.0.10 | 3.0.10 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of GHSA-5cf7-cxrf-mq73 is considered high due to the impact on private bouncer access.
To fix GHSA-5cf7-cxrf-mq73, upgrade to version 3.0.10 of the bostr package.
The impact of GHSA-5cf7-cxrf-mq73 allows unauthorized users to access the bouncer despite not being listed in authorized_keys.
GHSA-5cf7-cxrf-mq73 affects the bostr package versions prior to 3.0.10.
Yes, a patch for GHSA-5cf7-cxrf-mq73 is available in version 3.0.10 of the bostr package.