Skip to main content
Ask Ubuntu

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • So i can consider that if an em dash is present in the CVE field for ubuntu version N, it is not vulnerable to the CVE? I was wondering if it meant end of life for security support but the component could still be vulnerable Commented Oct 10, 2023 at 14:50
  • 1
    It's possible that Ubuntu version N is vulnerable to the CVE, but we haven't been informed of that in the CVE tracker table because it is not reported. It's also possible that the bug was fixed in later versions of Ubuntu. Commented Oct 10, 2023 at 15:00
  • 1
    @DenLi This is where you might want to read the page for the CVE itself and see what "affected versions" there are. If it's already been patched and included in Upstream and Ubuntu releases, chances are they stop tracking after that point because its fixes are already included. Which is the case for a lot of old CVEs like the one there. You have a specific example in another post by you - CVE-2017-6519. I answered that thread giving you a deep-dive into how I'd dissect and analyze it, rather than using that 'returned table' from the search itself. Commented Oct 10, 2023 at 15:06
  • Thank you for your detailed answer. Of course, i checked the CVE page. I just didn't understand the security release process yet Commented Oct 10, 2023 at 16:00