Zarro Technology · Security briefing
Today’s briefing highlights an SSH authentication bypass affecting specific Alpine/musl configurations and a critical Rails attachment-processing vulnerability. Neither cited vendor notice establishes active exploitation; exposed configurations still need prompt remediation.
Alpine’s 5 November advisory affects systems running OpenSSH without PAM password checks, with password authentication enabled, an account whose password field is an asterisk, and another local account with a SHA-256/SHA-512 password hash. Key-only accounts can consequently become reachable without the intended credentials. Root’s default password-login restriction still matters; other accounts may have elevation rights.
Inventory Alpine hosts and containers that actually run sshd. Alpine identifies releases 3.16–3.24 and edge; install its fixed OpenSSH package and restart the daemon. Upstream mitigation is in OpenSSH 10.6p2. Updating the package alone leaves the old daemon running.
If updating is delayed, disable password authentication in the server configuration. Confirm working key access and recovery-console access first, validate the configuration, then restart sshd using your deployment procedure. The server setting is:
PasswordAuthentication noContainers without sshd and systems already disabling password authentication are outside the described exposure. Review successful password logins for accounts intended to accept keys only; investigate anomalies rather than treating a quiet log as proof of safety. The vendor notice had no CVE assigned when written and provides no campaign-specific IoCs. Critical follows OpenSSH’s qualitative security assessment.
Sources: Alpine: affected conditions, exclusions and immediate remediation · OpenSSH: 10.6p2 release notes
Rails’ 4 November advisory affects applications accepting untrusted uploads and processing attachments with ImageMagick under an insufficiently restrictive policy. Crafted attachments can permit arbitrary file writes; Disk storage can also expose files readable by the application, including secrets. The advisory rates the issue CVSS 3.0 9.8, but lists no known CVE.
Update activestorage below 8.0.5.2 to 8.0.5.2, or affected 8.1 releases below 8.1.4.1 to 8.1.4.1. MiniMagick deployments require mini_magick 5.1 or later for the shipped policy. Verify attachment processing after deployment, especially PDF/PostScript workflows or customised MiniMagick environments.
The maintainer directs affected Disk-service deployments to rotate secret_key_base and every secret readable by the application process, including master keys, database/storage credentials and third-party tokens. Do not retain exposed secrets as fallbacks. Follow the advisory’s ImageMagick policy workaround if an upgrade is delayed. No campaign IoCs are published; preserve unexpected file changes and upload-processing anomalies for investigation.
Sources: Rails: exposure requirements, fixed versions and secret rotation
Zarro Technology