Johnson Controls Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Type

The moderation team is working with the threat intelligence team to categorize software that is affected by security vulnerabilities. This helps to illustrate the assignment of these categories to determine the most affected software types.

Product

Johnson Controls Metasys ADX9
Johnson Controls Metasys ADS8
Johnson Controls Metasys OAS8
Johnson Controls Metasys3
Johnson Controls OpenBlue Enterprise Manager Data ...2

Grouping vulnerabilities by products helps to get an overview. This makes it possible to determine an homogeneous landscape or the most important hotspots in heterogeneous landscapes.

Remediation

Official Fix20
Temporary Fix0
Workaround0
Unavailable0
Not Defined6

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High0
Functional0
Proof-of-Concept0
Unproven0
Not Defined26

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined0
Physical0
Local0
Adjacent3
Network23

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined0
High0
Low11
None15

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined0
Required6
None20

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤20
≤30
≤40
≤51
≤68
≤710
≤86
≤91
≤100

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤20
≤30
≤40
≤51
≤69
≤710
≤85
≤91
≤100

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤20
≤30
≤46
≤56
≤64
≤76
≤84
≤90
≤100

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤30
≤40
≤50
≤62
≤76
≤82
≤90
≤101

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤20
≤30
≤40
≤51
≤62
≤70
≤85
≤98
≤102

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k4
<2k11
<5k11
<10k0
<25k0
<50k0
<100k0
≥100k0

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k22
<2k4
<5k0
<10k0
<25k0
<50k0
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Products (17): American Dynamics Victor Web Client (1), C-CURE 9000 (1), CEM Systems AC2000 (1), CKS CEVAS (1), Facility Explorer SNC Series Supervisory Controller (1), IQ Wifi 6 (1), KT-1 (1), Metasys (3), Metasys ADS (8), Metasys ADX (9), Metasys OAS (8), Metasys Reporting Engine (1), OpenBlue Enterprise Manager Data Collector (2), Software House C-CURE Web Client (1), System Configuration Tool (2), exacqVision Enterprise Manager (1), exacqVision Web Service (1)

PublishedBaseTempVulnerabilityProdExpRemCTIEPSSCVE
07/25/20237.37.2Johnson Controls IQ Wifi 6 excessive authenticationWireless LAN SoftwareNot DefinedOfficial Fix0.020.00091CVE-2023-3548
05/19/20235.35.2Johnson Controls OpenBlue Enterprise Manager Data Collector API information disclosureUnknownNot DefinedOfficial Fix0.030.00049CVE-2023-2025
05/19/20238.38.2Johnson Controls OpenBlue Enterprise Manager Data Collector API improper authenticationUnknownNot DefinedOfficial Fix0.040.00087CVE-2023-2024
02/10/20235.85.7Johnson Controls System Configuration Tool missing secure attributeUnknownNot DefinedOfficial Fix0.000.00054CVE-2022-21940
02/10/20235.65.5Johnson Controls System Configuration Tool cookie httponly flagUnknownNot DefinedOfficial Fix0.000.00054CVE-2022-21939
01/13/20236.56.5Johnson Controls Metasys ADS/Metasys ADX/Metasys OAS API insufficiently protected credentialsUnknownNot DefinedOfficial Fix0.020.00087CVE-2021-36204
10/28/20226.86.7Johnson Controls CKS CEVAS cross site scriptingUnknownNot DefinedOfficial Fix0.050.00050CVE-2021-36206
10/05/20227.37.2Johnson Controls Metasys ADX User Identity Claim improper authenticationUnknownNot DefinedOfficial Fix0.050.00053CVE-2022-21936
07/22/20225.35.2Johnson Controls Metasys ADS/Metasys ADX/Metasys OAS Web API missing authenticationUnknownNot DefinedOfficial Fix0.030.00075CVE-2021-36200
06/16/20225.85.7Johnson Controls Metasys ADS/Metasys ADX/Metasys OAS MUI Graphics Web Interface cross site scriptingUnknownNot DefinedOfficial Fix0.070.00053CVE-2022-21938

16 more entries are not shown

Might our Artificial Intelligence support you?

Check our Alexa App!