News for hackers. Stuff that matters.
Re:Zero-Day Exploitation of Atlassian Confluence by yardstick on Friday June 03, 2022 @04:05AM (#31605539)
They’ve suggested blocking ${ in the request
Re:Zero-Day Exploitation of Atlassian Confluence by Icingdeath on Friday June 03, 2022 @05:16AM (#31605980)
Using nginx in front of my local confluence server (not listening on the internet) and used the following:

  location ~\* \$\{. {
          deny all;
  }
but this only helps if this vulnerability is triggered using the request uri otherwise it's useless
Re:Zero-Day Exploitation of Atlassian Confluence by bombcar on Friday June 03, 2022 @09:31AM (#31607991)
Anyone know how you'd quote it for Apache rewrite?

        RewriteEngine On
        RewriteCond %{REQUEST_URI} ^.*\${.*$
        RewriteRule ^/(.*) https://google.com [R=302,L]
seems to work ...
Re:Zero-Day Exploitation of Atlassian Confluence by justin_oaks on Friday June 03, 2022 @09:29AM (#31607952)
The security advisory from Atlassian says blocking ${ "may reduce your risk". That's a far cry from being a fix.
Re:Zero-Day Exploitation of Atlassian Confluence by technion on Friday June 03, 2022 @09:39AM (#31608104)
I really worry about these sort of claims. I'm seeing pushback from people about shutting servers down because it's insisted "a WAF is protecting us now", and that's based on a "may reduce risk".
Re:Zero-Day Exploitation of Atlassian Confluence by tyingq on Friday June 03, 2022 @03:48PM (#31612813)
I would worry about just using that blocking pattern. They mention OGNL injection and ${ is just one pattern you can go after. There's also #{, %{, #var, and more.
Re:Zero-Day Exploitation of Atlassian Confluence by richbell on Friday June 03, 2022 @11:21AM (#31609524)
Same issue with log4shell. "Why are you bugging us? We already applied <mitigation posted 2 weeks ago that has since been disproven>."
Re:Zero-Day Exploitation of Atlassian Confluence by jpetrucc on Friday June 03, 2022 @11:12AM (#31609399)
posting a snippet for HAProxy in case its helpful to someone else (or if others have recommendations on how to better do this)

  http-request deny if { path -m sub ${ }
  http-request deny if { query -m sub ${ }
  http-request deny if { path -m sub $%7B }
  http-request deny if { query -m sub $%7B }
  http-request deny if { path -m sub %24%7B }
  http-request deny if { query -m sub %24%7B }