5 ms·

How about this: a "vulnerability" is a "vulnerability", but after it was identified and verified to cause problem, that's when it should be called a "bug", beca

• sfink 4mo ago
  At Mozilla, everything is called a bug. It's what other systems call an "issue". So it's too late for your terminology at Mozilla. (Example: I have a bug to improve the HTML output of my static analysis tool. There is nothing incorrect or flawed about the current output.) At Mozilla, but not everywhere: exploits are a subset of vulnerabilities are a subset of bugs.
  • darkwater 4mo ago
    That's why they created Bugzilla :) (https://www.bugzilla.org/blog/2023/08/26/bugzilla-celebrates-25-years/ https://www.bugzilla.org/blog/2023/08/26/bugzilla-celebrates...)
  • freedomben 4mo ago
    Fwiw i think this is right. A bug is anything that doesn't do what you want it to do, and nobody should want a vulnerability in their software
• Yoric 4mo ago
  When I worked at Mozilla, _everything_ was called a bug, whether it was a software issue, a problem in the office or some paperwork missing. Much as GitHub calls everything an "issue" and GitLab a "work item".
• cassianoleal 4mo ago
  How is a vulnerability not a bug? Surely you didn’t design the software to enable exploits on your users, right? Vulnerabilities are a special class of bugs. One that’s generally so important to fix that they get a special name and more attention. That doesn’t make them less of a bug. It makes them more of one.