Saltar al contenido ForoHackers

Our site doesn't need old browser polyfills; it did keep the old script tag

Seguridad de la cadena de suministroSeguridad web
#11439 · · Citar · Denunciar

Sansec put out its polyfill.io findings today. Our template still invites that domain into every visitor's page, apparently because a retired widget once needed it. The page the widget lived on is a coffee rota. The script has quite the promotion. Who owns your footer?

#11603 · · Citar · Denunciar

A script loaded that way runs in the page's context. Users don't get a neat box around it saying "this bit can only do the rota". First thing I'd want to know is which templates included it.

#11604 · · Citar · Denunciar

social posts are turning this into a hundred thousand sites with ALL their visitors infected. do we have a count of people who actually got the malware, or a count of includes?

#11608 · · Citar · Denunciar

Sansec estimated over 100,000 sites included it. That doesn't tell us how many visitors actually received a malicious response. For us, retire the include, check the generated pages, then look for evidence of impact.

#11611 · · Citar · Denunciar

If it really is changing what it serves depending on the browser, a single integrity hash isn't some magical blessing for every variant. Pin a known file if that's what you mean to run.

#11612 · · Citar · Denunciar

The footer owner was the rota editor. She said "I schedule the washing-up, mate" and handed it back. Fair. We now have the dependency removal in the template tests.

#11627 · · Citar · Denunciar

found our old include in the event programme's print view as well. I'd have given the patched home page a big green tick yesterday and missed the second door entirely.

No has iniciado sesión, así que esto se publica como anónimo: no se guarda con ello ninguna cuenta, nombre ni dirección, y no puede llevar enlaces ni imágenes. Inicia sesión o únete para publicar con tu nombre. Los registros de nuestro servidor web guardan la dirección y la hora de cada petición hasta 14 días; para que la tuya no quede en ellos, usa Tor. Para escribir al equipo de forma confidencial, usa el buzón. Firmar como fuente habitual (una clave guardada solo en este navegador)

Enviar tarda unos segundos aquí: tu navegador resuelve antes una prueba de trabajo contra el spam.

Responder