TLS validation error

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• pivotal software spring advanced message queuing protocol1.0.0 and later · before 1.7.10
• pivotal software spring advanced message queuing protocol2.0.0 and later · before 2.0.6
• vmware rabbitmq java clientbefore 4.8.0
• vmware rabbitmq java client4.8.1 and later · before 5.4.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (dell). Independent of NVD's CPE analysis and usually ahead of it.

• Pivotal Spring AMQP

  • 1.x and later · before 1.7.10affected
  • 2.x and later · before 2.0.6affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Other highest-scoring records for the same primary product.

• CVE-2017-8045In Pivotal Spring AMQP versions prior to 1.7.4, 1.6.11, and 1.5.7, an org.springframework.amqp.core.Message may be unsafely deserialized whe
  40Plan

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {2  // Left empty for the test environment3}

1val client = OkHttpClient.Builder()2  .certificatePinner(3    CertificatePinner.Builder()4      .add("api.sirius.example", "sha256/…")5      .build()6  ).build()

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.