- October 25, 2017
- 1 min read
Automatically get latest Docker security vulnerabilities posted to slack channel
It's extremely important to always be aware of all the announcements related to security issues for the products you use and support within your company, If you use slack we can have all these announcements posted directly to a slack channel. In this post, I will go over how we can do just that for Docker.
Approach
You can get a list of known security vulnerabilities using www.cvedetails.com website. Known security vulnerabilities can be searched by the vendor, product, version etc.
Below RSS feed will provide you all known security vulnerabilities for Docker
http://www.cvedetails.com/vulnerability-feed.php?vendor_id=13534&orderby=3&cvssscoremin=0
If you want to further filter down by specific product or version you can simply add "product_id" and/or "version_id" to the query string. To find the product id or version id www.cvedetails.com site provides product search and version search capabilities, once you have found the product through the search capability you can simply copy the product id and/or version id from the address bar in your browser and include it in the query string for above RSS feed URL
From the above RSS feed URL vendor id "13534" is for Docker.
Create a slack channel named "docker" in your slack workspace where we can post all security vulnerabilities related to Docker as well as have all docker related discussions.
Copy the above RSS URL and issue following command in the slack channel.
/feed subscribe http://www.cvedetails.com/vulnerability-feed.php?vendor_id=13534&orderby=3&cvssscoremin=0Before you subscribe to RSS feed verify that it's not already subscribed by issuing command below which will list out all the RSS feeds that are already subscribed
/feed listOnce you receive an announcement you should evaluate it and if you are affected by it patch or mitigate the risk, test it and notify everyone.
Hope this helps...
Cheers,
Ram
Related Posts
RAM GOPINATHAN
September 17, 2026
Onboarding Edge Devices to FlightCTL with FIDO Device Onboarding
How I wired FDO's owner service, a bootc image layering go-fdo-client on the FlightCTL agent base, and two Ansible playbooks together so edge devices enroll into FlightCTL with zero manual steps.
RAM GOPINATHAN
September 14, 2026
Provisioning Devices and Onboarding to FlightCTL
Building a bootc image with the FlightCTL agent, baking it into an AMI, and provisioning EC2 test devices that inject their enrollment credentials via cloud-init and show up as pending enrollments in FlightCTL.
RAM GOPINATHAN
September 12, 2026
Deploying FlightCTL on EKS: Edge Fleet Management with Keycloak OIDC
A step-by-step walkthrough of standing up FlightCTL on Amazon EKS with Keycloak OIDC auth, ALB ingress, and a dedicated NLB for mTLS device enrollment.