Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

The following is a list of known EdgeX security issues and vulnerabilities – and any associated Common Vulnerabilities and Exposures (CVE) reports to accompany the issue. CVE is a program for identifying, cataloging and addressing software and firmware vulnerabilities (see https://cve.mitre.org/).  Nationally, the federal government runs the CVE program to help build a free, standardized list or dictionary of security vulnerabilities for organizations to use to improve their software’s exposure and posture to security threats.

EdgeX grades security issues on the CVSS(Common Vulnerability Scoring System) scale.  The four levels are critical, high, medium and low level issues.

ComponentDescriptionSeverityAffected ReleasesIssue LinkFix TimelineResolution/Mitigation 
Database - MongoDBMongoDB is one of the data persistence solutions useable in EdgeX. The MongoDB 3.4.9 container base image  has known vulnerabilities stemming from its underlying base Linux image and some from MongoDB source itself..Medium

Delhi

Edinburgh

https://www.cvedetails.com/vulnerability-list/vendor_id-12752/product_id-25450/version_id-229891/Mongodb-Mongodb-3.4.9.htmlFuji

Pulling 4.0-xenial MongoDB package, which starts with a Debian base image that does not include a host of insecurities spanning Perl, OpenSSL etc, and some MongoDB specific fixes.

https://github.com/edgexfoundry/docker-edgex-mongo/commit/2c86e5e4359367177dc339556604c3af6fb9ee2a

Database access credentials in the clear

MongoDB and Redis are the available data persistence layers in EdgeX. While the access credentials (username and password) are in the clear for MongoDB, located in the configuration service (aka Consul) or on the local file system, Redis defaults to no authentication.  High

Delhi

Edinburgh


Fuji

EdgeX-using organizations should turn on the database access controls and institute a means to secure the data access credentials provided to the services.


The issue has been resolved in EdgeX Fuji with credentials being created on the fly, saved in Vault and used during setup. Requires user to set secure mode on.

Go net package vulnerabilities

net/http: Denial of Service vulnerabilities (ping and reset) in the HTTP/2 implementation


and 

net/url in Go before 1.11.13 and 1.12.x before 1.12.8 mishandles malformed hosts in URLs, leading to an authorization bypass in some applications. This is related to a Host field with a suffix appearing in neither Hostname() nor Port(), and is related to a non-numeric port number.

High, High, Critical

Delhi

Edinburgh


https://nvd.nist.gov/vuln/detail/CVE-2019-9512

https://nvd.nist.gov/vuln/detail/CVE-2019-9514

https://nvd.nist.gov/vuln/detail/CVE-2019-14809

CVE-2019-9512 and CVE-2019-9514, and Go issue golang.org/issue/33606.

net/url: parsing validation issue

CVE-2019-14809 and Go issue golang.org/issue/29098.

Fuji
Docker: edgexfoundry/device-coap{-arm64}:2.0.0Multiple vulnerabilities due to accidental use of an obsolete base image12 High, 4 Medium, eachIrelandNo issue filedIreland (patch)Will republish edgexfoundry/device-coap{-arm64}:2.0.1 with updated base image or manually update Dockerfile use alpine:3.12 or later and rebuild.
GitHub: edgexfoundry/*/go.modVulnerabilities in golang.org/x/crypto/sshNumerous HighIreland

CVE-2020-9283 (improper signature verification)

Indeterminate (no fix available)SSH module is not directly used by EdgeX is not impacted by the vulnerability.  Additionally, the vulnerable package is pulled in through multiple dependency chains using a pseduo-version number. Not fixable until patch is available in a direct dependency of EdgeX.
GitHub: edgexfoundry/*/go.modVulnerabilities in golang.org/x/textHighIreland

CVE-2020-14040 (denial of service)

Indeterminate (no fix available)EdgeX does not directly call the vulnerable functions (UseBOM, ExpectBOM).  Additionally, the vulnerable package is pulled in through multiple dependency chains using a pseduo-version number. Not fixable until patch is available in a direct dependency of EdgeX.
GitHub: edgexfoundry/*/go.modVulnerabilities in github.com/dgrijalva/jwt-goHighIreland

CVE-2020-26160 (access restriction bypass)

Indeterminate (no fix available)Not exploitable.  This library is used by EdgeX to generate JWT tokens for the API gateway.  Token parsing (where the defect lies) is handled by the gateway (Kong). Thus, we are not susceptible.
GitHub: edgexfoundry/*/go.modVulnerabilities in github.com/miekg/dnsHighIreland

CVE-2019-19794 (insecure randomness)

Indeterminate (no fix available)Dependency chain is at least 5 components deep.  Unknown if exploitable.  Not fixable until patch is available in a direct dependency of EdgeX.
Docker: edgexfoundry/*(-arm64):2.0.[01]Vulnerability in Alpine 3.12 base imageCriticalIrelandCVE-2021-36159 (out-of-bound read by libfetch)JakartaNot expoitable.  EdgeX foundry binaries are statically linked and do not have runtime dependencies on libfetch.  Can be fixed locally by upgrading base image to latest Alpine version.
Docker: edgexfoundry/sys-mgmt-agent(-arm64):2.0.*Vulnerability in docker:20.10.8 base imageHighJakartaSNYK-ALPINE314-OPENSSH-1728379TBDNot exploitable.  ssh-keygen not used by sys-mgmt-agent.
GitHub: github.com/edgexfoundry/app-functions-sdk-go/v2Broken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectorsLow<= IrelandCVE-2021-41278JakartaBroken crypto in in the app-functions-sdk "AES" transform results in a level of protection significantly less than the user would expect.  As the broken transform is a library function that is not invoked by default, users who do not use the AES transform in their processing pipelines are unaffected. Those that are affected are urged to upgrade to the Jakarta EdgeX release and modify processing pipelines to use the new "aes256" transform.
Any EdgeX microservice that supports the /api/v2/config endpoint and supports connection to the EdgeX message bus (almost all of them).Configuration API in EdgeXFoundry 2.1.0 and earlier exposes message bus credentials to local unauthenticated usersModerate<= JakartaCVE-2022-31066

Jakarta (2.1.1)
Kamakura

The defect is resolved in Jakarta (2.1.1) and Kamakura (2.2.0) by injecting the message bus credential into a copy of the configuration structure that is not exported via the /api/v2/config endpoint.
Practically everything (introduced via go-mod-core-contracts)Parse() can panic due to improper index calculation.Medium<= JakartaSNYK-GOLANG-GOLANGORGXTEXTINTERNALLANGUAGE-2400718 (CVE-2021-38561) (out of bounds read)

Not vulnerable.  Requires test for "bcp47_language_tag" to trigger condition, which EdgeX does not check for.  Otherwise, harmless to upgrade go-playground/validator.

  • No labels