Readit News logoReadit News
uticus · 2 years ago
> When Rapid7 contacted JetBrains about their uncoordinated vulnerability disclosure, JetBrains published an advisory on the vulnerabilities without responding to Rapid7 on the disclosure timeline. JetBrains later responded to indicate that CVEs had been published.

Is this a failure on JetBrain's part to acknowledge the issue and properly give credit for discovering the CVE?

jeffmcjunkin · 2 years ago
Yup, silently patching (like JetBrains did) has a lot of downsides. Let alone the deception from JetBrains to the Rapid7 team.

(Disclosure: I know some of the folk on the Rapid7 side, so I'm perhaps biased towards their interpretation of events)

xmodem · 2 years ago
What deception are you referring to? I don't see anything in the linked article that I would consider to be an accusation of deception.

Deleted Comment

igor_akhmetov · 2 years ago
The full timeline for the side of JetBrains is described here: https://blog.jetbrains.com/teamcity/2024/03/our-approach-add...
uticus · 2 years ago
> Note: The JetBrains release blog for 2023.11.4 appears to display different publication dates based on the time zone of the reader. Some readers see that it was released March 3, while others see March 4. We've modified our language above to note that Rapid7 saw the release blog on March 4, regardless of what time it was released.

If the contention is when to release details, then should agree on UTC for all parties, with appropriate time precision. Anything else is adding obscurity to an already difficult-to-follow plot.

Deleted Comment