Skip to content

Improper mutual TLS configuration

Moderate
bjpbakker published GHSA-hqqc-pv86-g8j2 Jan 26, 2023

Package

ripencc/rpki-publication-server

Affected versions

< v2.0.0-rc1

Patched versions

v2.0.0-rc1

Description

Impact

Mutual TLS configuration in rpki-publication-server did not enforce mutual TLS for clients. While the software is deployed in trusted networks, this vulnerability contradicts assumptions of the security model the software is designed to be deployed in.

Patches

Has the problem been patched? What versions should users upgrade to?

v2.0.0-rc1

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

The application SHOULD be deployed where it is only accessible from a trusted network. Operators can also deploy the application together with a service proxy (e.g. envoy) that provides authentication.

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

CVE ID

No known CVE

Weaknesses