CVE-2019-6475: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-2gfp-93f7-f268
Share
CVSS 7.5
CWE-345
Published
Advisory Summary

CVE-2019-6475 is a HIGH (CVSS 7.5) security vulnerability vulnerability (CWE-345: Insufficient Verification of Data Authenticity) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.. Remediation is available in the latest vendor maintenance releases.

CVE-2019-6475 at a Glance

CVE Identifier CVE-2019-6475
GHSA Identifier GHSA-2gfp-93f7-f268
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-345: Insufficient Verification of Data Authenticity
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2019-6475

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2019-6475, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-345: Insufficient Verification of Data Authenticity, where the product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Mirror zones are a BIND feature allowing recursive servers to pre-cache zone data provided by other servers. A mirror zone is similar to a zone of type secondary, except that its data is subject to DNSSEC validation before being used in answers, as if it had been looked up via traditional recursion, and when mirror zone data cannot be validated, BIND falls back to using traditional recursion instead of the mirror zone. However, an error in the validity checks for the incoming zone data can allow an on-path attacker to replace zone data that was validated with a configured trust anchor with forged data of the attacker's choosing. The mirror zone feature is most often used to serve a local copy of the root zone. If an attacker was able to insert themselves into the network path between a recursive server using a mirror zone and a root name server, this vulnerability could then be used to cause the recursive server to accept a copy of falsified root zone data. This affects BIND versions 9.14.0 up to 9.14.6, and 9.15.0 up to 9.15.4.

References

NVD — CVE-2019-6475 NVD
https://nvd.nist.gov/vuln/detail/CVE-2019-6475
kb.isc.org/docs/cve-2019-6475 WEB
https://kb.isc.org/docs/cve-2019-6475
Software Security Information SECURITY
https://security.netapp.com/advisory/ntap-20191024-0004
support.f5.com/csp/article/k422385... WEB
https://support.f5.com/csp/article/K42238532?utm_source=f5support&amp%3Butm_medium=RSS
support.f5.com/csp/article/k422385... WEB
https://support.f5.com/csp/article/K42238532?utm_source=f5support&utm_medium=RSS

Frequently Asked Questions

What is CVE-2019-6475?
CVE-2019-6475 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-345: Insufficient Verification of Data Authenticity.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2019-6475?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2019-6475?
CVE-2019-6475 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.
What CWE is associated with CVE-2019-6475?
CVE-2019-6475 is classified under CWE-345: Insufficient Verification of Data Authenticity (The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.).
How can I check Maven dependencies for CVE-2019-6475?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2gfp-93f7-f268",
  "modified" : "2024-04-04T02:31:12Z",
  "published" : "2022-05-24T16:59:19Z",
  "aliases" : [ "CVE-2019-6475" ],
  "details" : "Mirror zones are a BIND feature allowing recursive servers to pre-cache zone data provided by other servers. A mirror zone is similar to a zone of type secondary, except that its data is subject to DNSSEC validation before being used in answers, as if it had been looked up via traditional recursion, and when mirror zone data cannot be validated, BIND falls back to using traditional recursion instead of the mirror zone. However, an error in the validity checks for the incoming zone data can allow an on-path attacker to replace zone data that was validated with a configured trust anchor with forged data of the attacker's choosing. The mirror zone feature is most often used to serve a local copy of the root zone. If an attacker was able to insert themselves into the network path between a recursive server using a mirror zone and a root name server, this vulnerability could then be used to cause the recursive server to accept a copy of falsified root zone data. This affects BIND versions 9.14.0 up to 9.14.6, and 9.15.0 up to 9.15.4.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2019-6475"
  }, {
    "type" : "WEB",
    "url" : "https://kb.isc.org/docs/cve-2019-6475"
  }, {
    "type" : "WEB",
    "url" : "https://security.netapp.com/advisory/ntap-20191024-0004"
  }, {
    "type" : "WEB",
    "url" : "https://support.f5.com/csp/article/K42238532?utm_source=f5support&amp%3Butm_medium=RSS"
  }, {
    "type" : "WEB",
    "url" : "https://support.f5.com/csp/article/K42238532?utm_source=f5support&utm_medium=RSS"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-345" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2019-10-17T20:15:00Z"
  }
}