🚨 Critical Java4Shell vulnerability allows hackers to remotely execute code in Jira, Confluence, Jenkins, and other major platforms; CVE-2026-114938
YouTube Video (attached): youtube.com/watch?v=-EOYmL4U…
Security researchers at Calif have disclosed a critical OpenJDK vulnerability (CVSS 9.2) that could allow unauthenticated attackers to steal sensitive server memory and execute malicious code remotely.
Dubbed Java4Shell, the flaw affects OpenJDK's Base64 decoder. Researchers successfully demonstrated remote code execution against Keycloak, Jira, Confluence, Jenkins, JFrog Artifactory, and PingFederate in their default configurations.
The vulnerability affects supported Java distributions running on certain x86-64 processors with AVX-512 support. Researchers used AI to discover the flaw in approximately one hour and develop a working exploit in two more hours.
Security updates are now available. Administrators are urged to patch immediately or disable the vulnerable Base64 optimization.
In short: deploying SRI on pinned/static third-party scripts + a restrictive CSP (or Integrity-Policy) would have prevented or immediately flagged this specific incident on protected sites.
Scott's own write-up on the incident reaches the same conclusion: SRI and CSP (especially with reporting) are the practical tools that exist today, visibility/detection is far better than nothing, full prevention is harder when the third-party JS is designed to change, and the industry still under-uses both.
Full enforcement can stop unauthorized loads or behaviors, but if you allow the the malovent origin, a content swap on that origin can still execute unless SRI is also applied. The old CSP require-sri-for directive never shipped; Integrity-Policy is the modern replacement that can require SRI site-wide.
Content Security Policy (CSP): A strict script-src (with nonces, hashes, or limited origins) controls which scripts can run and where they can load from.
For frequently changing dynamic JS, you must update the hash on every legitimate change (or use multiple allowed hashes), which many teams find operationally hard.
This would have blocked the modified malovent payload on any site that had pinned a known-good hash. It works extremely well for versioned/static third-party assets.
Subresource Integrity (SRI): Adding an integrity="sha384-..." attribute + crossorigin="anonymous" on the <script> tag makes the browser hash the fetched bytes and refuse to execute if they don’t match.
🚨 Deux investisseurs auraient perdu plus de 830 000 $ en cryptos après avoir téléchargé une FAUSSE application Ledger Live sur l'App Store d'Apple.
Une première victime aurait perdu 403 ETH, soit environ 739 000 $, tandis que la seconde se serait fait voler 1 300 SOL, évalués à 93 500 $.
Le piège était redoutablement simple. Persuadées d'utiliser l'application officielle, les victimes auraient saisi leur phrase de récupération, permettant aux escrocs de prendre le contrôle de leurs portefeuilles et de transférer leurs fonds.
“A linguagem política destina-se a fazer com que a mentira soe como verdade e o crime se torne respeitável, bem como a imprimir ao vento uma aparência de solidez.”. - Orwell
Quem, na verdade, está propagando a mentira?
Since Apple Music and Spotify designs are so boring, I built an iPhone Duo app called Duoamp that is a throwback to Winamp
Shake it and a new Winamp-style skin appears