I found myself talking about irresponsible disclosure of vulnerabilities quite a lot recently on other shows.
So I thought it might be interesting to talk to you lot about it.
Have you noticed this recent trend of people not waiting, not properly doing responsible disclosure?
There's been, I don't know, probably four or five recently where they've been disclosed in a completely uncontrolled way and before patches are available to users of distros and all kinds of stuff.
I've seen a bunch of articles, I would say, roughly recently that do not look like proper disclosure, but I've never really been involved in either a proper disclosure vulnerability or given one to me.
So I don't have a lot of experience in that area.
Isn't it supposed to be relatively straightforward? You as a researcher or just a random person finds this vulnerability in some open source code.
or even proprietary code, you contact the maintainer of that code through secure channels or mailing lists or whatever it is, tell them about it, they fix it, they push out patches, having coordinated with all of the relevant distros and stakeholders stakeholders yeah and then it goes public and you get the glory for finding it that's how it's supposed to work right
it's a little bit more like a negotiation process than you made it sound right so from the point of view of a maintainer you're busy doing all of your stuff And then someone contacts you and says, I found this thing.
And what they need from you initially is acknowledgement that it's real, right? They need to make sure that they are going to get the credit eventually, right? Because they've done all this work and they need reward for that.
And generally as a maintainer, often what you're thinking is, I don't have time to check whether this is real or not, but I have to make time.
Assuming you then do investigate and find that it's legitimate, you then need to negotiate timescales, right? So there are some norms for this.
The norm for this has been 90 days from when you disclosed it before.
If the maintainers of the software don't do anything about it, it's legitimate for you to just disclose it without it being patched.
But actually, in reality, the process is much more of a negotiation.
And it's like, okay, you've found something that's quite fundamental for us.
It's going to take us longer than 90 days to fix it.
You know, how about you hold off your blog post and then, you know, you hopefully come to a sensible agreement.
But the critical part of it is that the security researcher is going to get the credit and you're going to back them up that it was them that found the thing, right? And if that trust is there, then there is room for negotiation about that kind of thing.
And in some cases, it's not just that the researcher should get credit.
It's that the entity that could give credit has said they would also give money.
So they should also give that money instead of not giving them money and not giving credit.
Yeah, bug bounties we're talking about here.
Right.
I found myself talking about irresponsible disclosure of vulnerabilities quite a lot recently on other shows.
So I thought it might be interesting to talk to you lot about it.
Have you noticed this recent trend of people not waiting, not properly doing responsible disclosure?
There's been, I don't know, probably four or five recently where they've been disclosed in a completely uncontrolled way and before patches are available to users of distros and all kinds of stuff.
I've seen a bunch of articles, I would say, roughly recently that do not look like proper disclosure, but I've never really been involved in either a proper disclosure vulnerability or given one to me.
So I don't have a lot of experience in that area.
Isn't it supposed to be relatively straightforward? You as a researcher or just a random person finds this vulnerability in some open source code.
or even proprietary code, you contact the maintainer of that code through secure channels or mailing lists or whatever it is, tell them about it, they fix it, they push out patches, having coordinated with all of the relevant distros and stakeholders stakeholders yeah and then it goes public and you get the glory for finding it that's how it's supposed to work right
it's a little bit more like a negotiation process than you made it sound right so from the point of view of a maintainer you're busy doing all of your stuff And then someone contacts you and says, I found this thing.
And what they need from you initially is acknowledgement that it's real, right? They need to make sure that they are going to get the credit eventually, right? Because they've done all this work and they need reward for that.
And generally as a maintainer, often what you're thinking is, I don't have time to check whether this is real or not, but I have to make time.
Assuming you then do investigate and find that it's legitimate, you then need to negotiate timescales, right? So there are some norms for this.
The norm for this has been 90 days from when you disclosed it before.
If the maintainers of the software don't do anything about it, it's legitimate for you to just disclose it without it being patched.
But actually, in reality, the process is much more of a negotiation.
And it's like, okay, you've found something that's quite fundamental for us.
It's going to take us longer than 90 days to fix it.
You know, how about you hold off your blog post and then, you know, you hopefully come to a sensible agreement.
But the critical part of it is that the security researcher is going to get the credit and you're going to back them up that it was them that found the thing, right? And if that trust is there, then there is room for negotiation about that kind of thing.
And in some cases, it's not just that the researcher should get credit.
It's that the entity that could give credit has said they would also give money.
So they should also give that money instead of not giving them money and not giving credit.
Yeah, bug bounties we're talking about here.
Right.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.