CVE-2016-5349: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-5c44-q7pc-hwjg
Share
CVSS 5.5
CWE-200
Published
Advisory Summary

CVE-2016-5349 is a MODERATE (CVSS 5.5) security vulnerability vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.. Remediation is available in the latest vendor maintenance releases.

CVE-2016-5349 at a Glance

CVE Identifier CVE-2016-5349
GHSA Identifier GHSA-5c44-q7pc-hwjg
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.5

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

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

How to Fix CVE-2016-5349

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-2016-5349, 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-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. 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

The high level operating systems (HLOS) was not providing sufficient memory address information to ensure that secure applications inside Qualcomm Secure Execution Environment (QSEE) only write to legitimate memory ranges related to the QSEE secure application's HLOS client. When secure applications inside Qualcomm Secure Execution Environment (QSEE) receive memory addresses from a high level operating system (HLOS) such as Linux Android, those address have previously been verified as belonging to HLOS memory space rather than QSEE memory space, but they were not verified to be from HLOS user space rather than kernel space. This lack of verification could lead to privilege escalation within the HLOS.

References

NVD — CVE-2016-5349 NVD
https://nvd.nist.gov/vuln/detail/CVE-2016-5349
Software Security Information SECURITY
https://source.android.com/security/bulletin/2017-04-01
www.codeaurora.org/insufficient-memory... WEB
https://www.codeaurora.org/insufficient-memory-address-information-prevent-arbitrary-memory-access-qsee-secure-applications-cve
Software Security Information SECURITY
https://www.qualcomm.com/company/product-security/security-advisories
Software Security Information SECURITY
http://www.securityfocus.com/bid/97364
Software Security Information SECURITY
http://www.securitytracker.com/id/1038201

Frequently Asked Questions

What is CVE-2016-5349?
CVE-2016-5349 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2016-5349?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2016-5349?
CVE-2016-5349 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2016-5349?
CVE-2016-5349 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check Maven dependencies for CVE-2016-5349?
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-5c44-q7pc-hwjg",
  "modified" : "2022-05-17T02:33:13Z",
  "published" : "2022-05-17T02:33:13Z",
  "aliases" : [ "CVE-2016-5349" ],
  "details" : "The high level operating systems (HLOS) was not providing sufficient memory address information to ensure that secure applications inside Qualcomm Secure Execution Environment (QSEE) only write to legitimate memory ranges related to the QSEE secure application's HLOS client. When secure applications inside Qualcomm Secure Execution Environment (QSEE) receive memory addresses from a high level operating system (HLOS) such as Linux Android, those address have previously been verified as belonging to HLOS memory space rather than QSEE memory space, but they were not verified to be from HLOS user space rather than kernel space. This lack of verification could lead to privilege escalation within the HLOS.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2016-5349"
  }, {
    "type" : "WEB",
    "url" : "https://source.android.com/security/bulletin/2017-04-01"
  }, {
    "type" : "WEB",
    "url" : "https://www.codeaurora.org/insufficient-memory-address-information-prevent-arbitrary-memory-access-qsee-secure-applications-cve"
  }, {
    "type" : "WEB",
    "url" : "https://www.qualcomm.com/company/product-security/security-advisories"
  }, {
    "type" : "WEB",
    "url" : "http://www.securityfocus.com/bid/97364"
  }, {
    "type" : "WEB",
    "url" : "http://www.securitytracker.com/id/1038201"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2017-04-06T19:59:00Z"
  }
}