3 ms·
Your second paragraph doesn't hold after one minute spent reading the CVEs list.
by shakow 4mo ago
Your second paragraph doesn't hold after one minute spent reading the CVEs list.
- foldr 4mo agoNil references in Go aren't likely to be a source of CVEs. Dereferencing a nil reference is not undefined behavior in Go; it's guaranteed to panic.
- shakow 4mo agoNot all CVEs are RCE. This one[1] for instance is go's nil-dereference caused. [1] https://access.redhat.com/security/cve/cve-2025-29785 https://access.redhat.com/security/cve/cve-2025-29785
- foldr 4mo agoThis is a bug that could also happen in Rust if someone used 'unwrap', or if the code panicked for any other reason. You can have logic bugs in any language. Remember the Cloudflare outage of Nov 2025. It's also worth noting that the vulnerability you link to is a denial of service vulnerability. While yes, this is technically a vulnerability, it's not the sort of thing that people are usually worrying about in the context of null pointers. If features that give rise to DoS vulnerabilities are the ones to worry about, top of the list would have to be backtracking regex engines: https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS https://owasp.org/www-community/attacks/Regular_expression_D...