Skip to content

Security: RIOT-OS/RIOT

SECURITY.md

RIOT Security Policy

All security bugs reported will be silently fixed in master and backported to the previous release.

When CVE numbers are assigned to RIOT vulnerabilities, they are associated with CPE identifiers in the shape of cpe:2.3:o:riot-os:riot:<VERSION>.

Reporting a Vulnerability

If a security issue is discovered, please report it to security@riot-os.org. A response will be provided within one week. The issue will be tracked in the security mailing list. The original reporter will be included in the discussion of the issue. You can encrypt your report using gpg key id 44C6AE441172F88D3423E81F5F7964D0F4239033, also included at the bottom of this file.

Classification of a vulnerability

Unless the reporter explicitly requests not to do so, the RIOT security maintainers may declassify an issue if the issue is not deemed critical -- for example when it requires an unlikely combination of circumstances and/or configuration options, or when it can only be exploited by a user who gains no additional privileges.

Notification of a Vulnerability

After a fix is provided the security issue will be privately disclosed to the original reporter, RIOT security maintainers, and "Trusted RIOT Users". A public announcement of the security fix will be made two weeks after the point release, though this may vary depending on the severity and ability of trusted RIOT users to provide the fix.

Trusted RIOT Users

To access the "Trusted RIOT Users" notifications on the RIOT forum please send information on the RIOT based service or product as well as your forum username to the security mailing list. Early notification of security bugs will be available and should not be shared publicly. If done, it will result in access removal from the "Trusted RIOT Users" notifications.

RIOT community GPG key

-----BEGIN PGP PUBLIC KEY BLOCK-----

mDMEYY4plhYJKwYBBAHaRw8BAQdALRZ/IJmifuwoSUYTVbKUy9z/m3y0ux6DLMD6
kMs13/+0J1JJT1QtT1Mgc2VjdXJpdHkgPHNlY3VyaXR5QHJpb3Qtb3Mub3JnPoiW
BBMWCAA+FiEERMauRBFy+I00I+gfX3lk0PQjkDMFAmGOKZYCGwMFCQPCZwAFCwkI
BwIGFQoJCAsCBBYCAwECHgECF4AACgkQX3lk0PQjkDMyggEA4lp3RDz+qj1K1veV
AlTh/L90rft7v7hZ9ROWD8mssD8BAI3sc+AESdkNf9lATsuH39/9jIi3CqLDdDxK
TJ9SQwcNiQIzBBABCAAdFiEEZi0l9uxO8DMbg2ZS/bt7xc+P5tsFAmGOKbkACgkQ
/bt7xc+P5tvQLA//fCVUg3B5N5J1gCOSGRlplzFO0DELNl8akecxxFuCUU74Hjyc
NSR4r8lQGhGvAVZLanBTprTWeYXtCuLAFfCwvNitbWXnmXRJawQ4k0TQfUXWNsbf
o84QHtKvxEEwLnubVfz+uATw0eahmU2beh2lEl1PKPnpnvc2q9eM019Ff7RV1poe
UD2ctDZ9yn1GDN6A1E9ejAqxowwPxZfafH6uvPcGnDtvBZ0SB2x+EXvFNDpdaFBm
GEqAOY+wBabk6XV9B5qhu0KeVy0ePHni8JaZQJZX+xo2Nzk14IG66nxBF0zz0qTj
2hntxygrS44lQffqkDl+W/Vyc31/k3vsemLQAaC+/ZV1ULxew1VCmBHKE201+8bS
VmQweoiVBa30HtftOhMtlSi+WHyzwG7KGiD148PJIuQx42Dj/iY0MLHCR5c32giF
tW0xJ6fDkVVC0LkLPfBbMJrKxpX5xyWnWVibWHyAXaI/Sh2oK9uIkvdPFh+rWNe7
Wr3Sokn3oUUE2BVkcOiZO9gMYngx6sDWazYwBMTaDxPISIdQofAPZ3LiW/f12wXq
V39RPXrlR3wDf8frhb8Jfxt1q0KHRbU3Drf8cGjpC42H/HazhH4QugbqfUv3BH0C
zJTYg+S79aDgIqUaW5ASxIi5e20jNKoaRnYg7Y1rYk4ttMtH72XylP1vuCK4OARh
jimWEgorBgEEAZdVAQUBAQdAQCSgXzft+sMtSz1vOEaT/s28u/LVmLjUoGtuAcns
in0DAQgHiH4EGBYIACYWIQRExq5EEXL4jTQj6B9feWTQ9COQMwUCYY4plgIbDAUJ
A8JnAAAKCRBfeWTQ9COQM+6YAP4w2R2qD9yO7ILcDWVyityM7+rmYrpqabbz07kh
CST7fgEAgvz7lVIT4bq7IqhdvcpOERC0Wu9c4AjyX9Y6KB3kIwI=
=3GfE
-----END PGP PUBLIC KEY BLOCK-----
Learn more about advisories related to RIOT-OS/RIOT in the GitHub Advisory Database