2 ms·
> multiple current employees’ data, including names, email addresses, work departments and other information. What was the hack, scraping LinkedIn? In all ser
by hn_throwaway_99 4y ago
> multiple current employees’ data, including names, email addresses, work departments and other information.
What was the hack, scraping LinkedIn?
In all seriousness, I feel like we need some different language or a color-coded system (ugh, kinda hate that after I just typed this) for the severity of information in hacks. All of this information listed is semi-public anyway. Birthdates/SSNs/private info I can understand getting up in arms about. But names and email addresses? Wait until younger folks hear about this giant book phone companies used to deliver that had nearly everyone's name and phone number in it!
- layer8 4y ago> What was the hack, scraping LinkedIn? I feel like we need some different language or a color-coded system for the severity of information in hacks. No, we just need to read the article.
- re-thc 4y agoOften the hardest part /s
- tyingq 4y agoThey had access to a visitor management system, which may turn out to be fairly interesting. Not the crown jewels, but who is visiting, and how often can be sensitive.
- IncRnd 4y ago> In all seriousness, I feel like we need some different language or a color-coded system (ugh, kinda hate that after I just typed this) for the severity of information in hacks. There already is language for this, but what we often have on HN are people posting random and old links to online newpaper articles that don't convey enough information about the vulnerability, its root cause, or its effect. In this case, there isn't a vulnerability score, because there isn't a disclosed vulnerability or exploit. However, there may be some risk that people outside Atlassian are unaware. CVSS scoring is used in many places. There are calculators that score a vulnerability in the context of a base score, temporal score, or environmental score. [1] Here is NIST's NVD page. [2] At the bottom are some of the most recently scored vulnerabilities. If we search for Atlassian tagged vulnerabilities at the NVD site[3], we see that the most recent vulnerability, CVE-2023-26256[4], actually is ranked high at 7.5 on the v3.1 CVSS scoring. There is an actual description. Plus there are references to advisories/solutions/tools, the CWE, a listing of affected software configurations, and a change history. [1] https://www.first.org/cvss/calculator/3.1 https://www.first.org/cvss/calculator/3.1 [2] https://nvd.nist.gov/ https://nvd.nist.gov/ [3] https://nvd.nist.gov/vuln/search/results?form_type=Basic&results_type=overview&query=atlassian&search_type=all&isCpeNameSearch=false https://nvd.nist.gov/vuln/search/results?form_type=Basic&res... [4] https://nvd.nist.gov/vuln/detail/CVE-2023-26256 https://nvd.nist.gov/vuln/detail/CVE-2023-26256