CVE-2016-8657

Public on

Last Modified: UTC

Description

It was discovered that EAP packages in certain versions of Red Hat Enterprise Linux use incorrect permissions for /etc/sysconfig/jbossas configuration files. The file is writable to jboss group (root:jboss, 664). On systems using classic /etc/init.d init scripts (i.e. on Red Hat Enterprise Linux 6 and earlier), the file is sourced by the jboss init script and its content executed with root privileges when jboss service is started, stopped, or restarted.

It was discovered that EAP packages in certain versions of Red Hat Enterprise Linux use incorrect permissions for /etc/sysconfig/jbossas configuration files. The file is writable to jboss group (root:jboss, 664). On systems using classic /etc/init.d init scripts (i.e. on Red Hat Enterprise Linux 6 and earlier), the file is sourced by the jboss init script and its content executed with root privileges when jboss service is started, stopped, or restarted.

Statement

It was found that a variant of the Tomcat CVE-2016-6325 exploit is also applicable to Red Hat JBoss Enterprise Application Platform 5 and 6. CVE-2016-8567 addresses these problems with JBoss EAP. The complexity is high as EAP has many files and configuration options. The issue is now corrected in JBoss Enterprise Application Platform EAP 6.4.14. For further information please refer https://access.redhat.com/articles/3016681

It was found that a variant of the Tomcat CVE-2016-6325 exploit is also applicable to Red Hat JBoss Enterprise Application Platform 5 and 6. CVE-2016-8567 addresses these problems with JBoss EAP. The complexity is high as EAP has many files and configuration options. The issue is now corrected in JBoss Enterprise Application Platform EAP 6.4.14. For further information please refer https://access.redhat.com/articles/3016681

Additional information

  • Bugzilla 1400343: jboss: jbossas writable config files allow privilege escalation
  • CWE-732: Incorrect Permission Assignment for Critical Resource
  • FAQ: Frequently asked questions about CVE-2016-8657

Common Vulnerability Scoring System (CVSS) Score Details

Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v3
CVSS v3 Score Breakdown
Red HatNVD

CVSS v3 Base Score

7.8

7.8

Attack Vector

Local

Local

Attack Complexity

Low

Low

Privileges Required

Low

Low

User Interaction

None

None

Scope

Unchanged

Unchanged

Confidentiality Impact

High

High

Integrity Impact

High

High

Availability Impact

High

High

CVSS v3 Vector

Red Hat: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

NVD: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS v2

Understanding the Weakness (CWE)

CWE-732

Confidentiality

Technical Impact: Read Application Data; Read Files or Directories

An attacker may be able to read sensitive information from the associated resource, such as credentials or configuration information stored in a file.

Access Control

Technical Impact: Gain Privileges or Assume Identity

An attacker may be able to modify critical properties of the associated resource to gain privileges, such as replacing a world-writable executable with a Trojan horse.

Integrity,Other

Technical Impact: Modify Application Data; Other

An attacker may be able to destroy or corrupt critical data in the associated resource, such as deletion of records from a database.

Frequently Asked Questions

Why is Red Hat's CVSS v3 score or Impact different from other vendors?

My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?

What can I do if my product is listed as "Will not fix"?

What can I do if my product is listed as "Fix deferred"?

What is a mitigation?

I have a Red Hat product but it is not in the above list, is it affected?

Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?

Want to get errata notifications? Sign up here.