#
Mastodon #
security #
issuefound by Cure53 as part of an audit performed at Mozilla's request
https://github.com/mastodon/mastodon/security/advisoriesUsing carefully crafted media files, attackers can cause Mastodon's media processing code to create arbitrary files at any location.
Impact: This allows attackers to create and overwrite any file Mastodon has access to, allowing Denial of Service and arbitrary Remote Code Execution.
https://github.com/mastodon/mastodon/security/advisories/GHSA-9928-3cp5-93fmFor anybody wondering what the Mastodon security issue is - CVE-2023-36460, you can send a toot which makes a webshell on instances that process said toot.
https://cyberplace.social/@GossiTheDog/110667416012211236When performing outgoing HTTP queries, Mastodon sets a timeout on individual read operations, but a malicious server can indefinitely extend the duration of the response through slowloris-type attacks.
Impact: This vulnerability can be used to keep all Mastodon workers busy for an extended duration of time, leading to the server becoming unresponsive
https://github.com/mastodon/mastodon/security/advisories/GHSA-9pxv-6qvf-pjwcUsing carefully crafted oEmbed data, an attacker can bypass the HTML sanitization performed by Mastodon and include arbitrary HTML in oEmbed preview cards.
Impact: This introduces a vector for Cross-site-scripting (XSS) payloads that can be rendered in the user's browser when a preview card for a malicious link is clicked through.
https://github.com/mastodon/mastodon/security/advisories/GHSA-ccm4-vgcc-73hpThere’s no action individual Mastodon users need to take other than to ensure that the instance they’re subscribed to has installed the updates.
Like Us
QRator
