54 ms·
Java may be memory safe, but errors in highly expressive functionality like Java serialization and expression parsers have been responsible for some of the most
by nneonneo 3y ago
Java may be memory safe, but errors in highly expressive functionality like Java serialization and expression parsers have been responsible for some of the most impactful vulnerabilities in recent memory.
CVE-2017-5638 was famously exploited to gain access to Equifax's network and cause a massive data breach. Log4Shell is continuing to cause problems in all kinds of networks due to the extremely widespread use of the Log4j library. Java is definitely an upgrade over C/C++, but there are definitely still security risks.
- pjmlp 3y agoWhen we eliminate 70% of CVE, it doesn't mean the remaining 30% shouldn't be taken care of.
- nmilo 3y agoSo then memory safety isn't the end-all be-all for security anyways. What do you suggest we use instead?
- gilcot 3y agoAda?
- irundebian 3y agoAda/SPARK
- a1o 3y agoCoq