News for hackers. Stuff that matters.

A comment on Dozens of malicious PyPI packages discovered targeting developers. Parent comment

Re:Dozens of malicious PyPI packages discovered targeting de... by rileymat2 on Wednesday November 02, 2022 @05:52PM (#33443414)
I thought that Java Applets (and maybe flash, I am less familiar) had an advanced security model, but it was exploit after exploit because of the huge attack surfaces?

I suspect you may run into similar sandbox escapes once things are complicated enough. So it seems like a good idea if they can be made bug free, but good luck with that?

[ Parent | on HN ]
Re:Dozens of malicious PyPI packages discovered targeting de... by erustemi on Wednesday November 02, 2022 @06:06PM (#33443573)
Maybe the issue was with how powerful and unrestricted reflection was in java before introduction of modules.
[ Parent | on HN ]
Re:Dozens of malicious PyPI packages discovered targeting de... by insanitybit on Wednesday November 02, 2022 @05:58PM (#33443476)
Part of the problem with the Java sandbox is that it was enforced entirely by the VM + the VM is written in C++. The idea is not inherently bad.
[ Parent | on HN ]
Re:Dozens of malicious PyPI packages discovered targeting de... by nl on Wednesday November 02, 2022 @06:21PM (#33443715)
It's been a while since I worked in this area but my recollection was that most JVM security issues in this areas were bypasses of the Java Security Manager often by confusing it about code origin. That's all Java code, not C++.
[ Parent | on HN ]
Re:Dozens of malicious PyPI packages discovered targeting de... by insanitybit on Wednesday November 02, 2022 @06:26PM (#33443752)
It's been so long I could be remembering incorrectly.
[ Parent | on HN ]
Re:Dozens of malicious PyPI packages discovered targeting de... by int_19h on Thursday November 03, 2022 @06:52AM (#33449251)
For both Java and .NET, there were actual verification bugs, as well - when bytecode that's not supposed to be valid gets past the verifier and results in e.g. mistyped references (which can then be used for all kinds of creative vtable abuse). Sometimes it can even be a bug in the VM spec itself, because implications of two different features interacting weren't fully considered.

But, yes, we've tried this idea many times now, and it never held up for long.

[ Parent | on HN ]