How many CVEs have patched OutgoingTLSConfig?

1 published CVEs changed OutgoingTLSConfig in hashicorp/consul, in 2 distinct patches totalling 4 changed lines, between 2018 and 2018.

What is the latest CVE that changed OutgoingTLSConfig?

CVE-2018-19653 (HashiCorp Consul can use cleartext agent-to-agent RPC communication), published 2018-12-09, changed lines 128 of tlsutil/config.go.

How does OutgoingTLSConfig compare to the rest of hashicorp/consul?

hashicorp/consul has 19 CVEs with a located fix in total; 1 of them changed OutgoingTLSConfig.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

hashicorp/consul

Function

OutgoingTLSConfig

Name: OutgoingTLSConfig in hashicorp/consul: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

tlsutil/config.go

Last patched December 9, 2018

1

CVEs

That changed this function

2

Distinct patches

Backports counted once

4

Lines changed

Added plus removed

2018

Years

By CVE publication date

Overview

OutgoingTLSConfig in hashicorp/consul was changed by 1 published CVE fixes in 2018, in 2 distinct patches that added or removed 4 lines in total.

hashicorp/consul has 19 CVEs with a located fix in total, so 5% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed OutgoingTLSConfig, newest first, with the lines each fix touched.

HashiCorp Consul can use cleartext agent-to-agent RPC communication
CVE-2018-19653 · line 128 · +0 −4
Medium · CVSS 5.9
EPSS 1.2%2018-12-09

Get an alert when the next CVE fix lands in hashicorp/consul, with the patched functions.

Monitor consul CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in hashicorp/consul changed by the most CVE fixes.

Build2 CVEs · agent/config/builder.go TokenRead2 CVEs · agent/consul/acl_endpoint.go Start2 CVEs · agent/agent.go Validate2 CVEs · agent/structs/config_entry_mesh.go validate2 CVEs · agent/structs/config_entry_intentions.go GetHTTP2 CVEs · agent/structs/config_entry_mesh.go

All patched functions in hashicorp/consul

Frequently asked questions

Common questions about CVE fixes to OutgoingTLSConfig.

How many CVEs have patched OutgoingTLSConfig?: 1 published CVEs changed OutgoingTLSConfig in hashicorp/consul, in 2 distinct patches totalling 4 changed lines, between 2018 and 2018.
What is the latest CVE that changed OutgoingTLSConfig?: CVE-2018-19653 (HashiCorp Consul can use cleartext agent-to-agent RPC communication), published 2018-12-09, changed lines 128 of tlsutil/config.go.
How does OutgoingTLSConfig compare to the rest of hashicorp/consul?: hashicorp/consul has 19 CVEs with a located fix in total; 1 of them changed OutgoingTLSConfig.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track hashicorp/consul CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing