Re: Potential security issues with EdgeX

Beau Frusetta

We can potentially help out in regards to code analysis. Let’s chat more next week in Edinburgh…


From: EdgeX-TSC-Security@... [mailto:EdgeX-TSC-Security@...] On Behalf Of David Ferriera
Sent: Thursday, October 18, 2018 13:32
To: Alexandre Courouble <acourouble@...>; edgex-tsc-security@...
Cc: Malini Bhandaru <mbhandaru@...>
Subject: Re: [Edgex-tsc-security] Potential security issues with EdgeX


Hi Alex,


    Thank you for the effort.  We welcome contributions.  We are always shorthanded in the security group.


   Code analysis has been on our list since the beginning.  If you have the resources to help us fix these and others, that would be great.  We would like to have this function be a part of our ongoing release process.


   Will you or any of your team be at the Edinburgh F2F next week?  If not, I will put this topic on one of our weekly meetings and invite you to discuss.





David Ferriera | Forgerock

Senior Director, Cloud Technology | Office of the CTO

m +1 408.454.8189 | w


On October 16, 2018 at 4:17:11 PM, Alexandre Courouble (acourouble@...) wrote:



Gosec (  is a tool that parses the source code and looks for security anti-patterns.


We ran gosec against the EdgeX-go source code and uncovered a series of potential vulnerabilities including but not limited to:


  • Blacklisted import crypto/sha1: weak cryptographic primitive
  • Potential file inclusion via variable
  • Expect file permissions to be 0600 or less


I’ve attached the gosec output to this email.


Do these vulnerabilities seem critical to you? If so, we would love to contribute fixes.


We would like to know how we should proceed further?


Potentially we could integrate gosec into the build pipeline.


Best regards,


Alex Courouble

Member of Technical Staff – Open Source Engineer

VMware Open Source Technology Center

Join to automatically receive all group messages.