This vulnerability, hidden within the netfilter: nf_tables component, allows local attackers to escalate their privileges and potentially deploy ransomware, which could severely disrupt enterprise systems worldwide.

you are viewing a single comment's thread
view the rest of the comments
[+] -13 points 1 year ago (37 children)

Lol. You have no idea what you are talking about about here πŸ˜‚

  • source
  • parent
  • hideshow 37 child comments
  • [–] 22 points 1 year ago* (19 children)

    Granted, I was mostly shit posting. But in all seriousness: wouldn't Rust prevent that kind of exploit by inherent design?

    Due to Rust’s ownership semantics, when we free a value, we relinquish ownership on it, which means subsequent attempts to use the value are no longer valid.

    https://stanford-cs242.github.io/f18/lectures/05-1-rust-memory-safety.html

  • source
  • parent
  • hideshow 19 child comments
  • [–] 1 point 1 year ago (2 children)

    Rust still has memory related bugs

  • source
  • parent
  • hideshow 2 child comments
  • [–] 7 points 1 year ago (1 child)

    This is correct, but not what most people think. For example, memory leaks could be considered bugs and it is easy to leak memory memory in safe rust on purpose.

    Memory leaks are usually not disastrous for security, mostly an issue for availability, sometimes.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 1 year ago

    I think a lot of the confusion comes from the ambiguity of the phrase "memory leak." Rust is designed around preventing insecure memory access (accessing out of bounds for an array, use-after-free, etc.) and devs call that a memory leak. But another form of memory leak is just not freeing up memory when its no longer needed (e.g. continuously pushing a bunch of things to a global vector and never clearing it). That is more of a fundamental program design issue that rust can't do anything about. (and really, neither could any turing complete language)

  • source
  • parent
  • load more comments (16 replies)
  • load more comments (33 replies)