Plesk Onyx 17.8.11 Amazon AWS Firehose accessKeyId/secretAccessKey exposure of resource ⚔ [Disputed]

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.5$0-$5k0.00

Summaryinfo

A vulnerability was found in Plesk Onyx 17.8.11 and classified as critical. The affected element is an unknown function of the component Amazon AWS Firehose. Executing a manipulation of the argument accessKeyId/secretAccessKey can lead to an unknown weakness. This vulnerability is tracked as CVE-2023-43784. No exploit exists. There are still doubts about whether this vulnerability truly exists.

Detailsinfo

A vulnerability classified as critical was found in Plesk Onyx 17.8.11 (Hosting Control Software). This vulnerability affects an unknown code of the component Amazon AWS Firehose. The manipulation of the argument accessKeyId/secretAccessKey with an unknown input leads to a unknown weakness. The CWE definition for the vulnerability is CWE-668. The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource. The impact remains unknown. CVE summarizes:

** DISPUTED ** Plesk Onyx 17.8.11 has accessKeyId and secretAccessKey fields that are related to an Amazon AWS Firehose component. NOTE: the vendor's position is that there is no security threat.

The weakness was disclosed 09/22/2023. The advisory is available at docs.aws.amazon.com. This vulnerability was named CVE-2023-43784 since 09/22/2023. Technical details are known, but there is no available exploit.

The real existence of this vulnerability is still doubted at the moment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.5

VulDB Base Score: 5.5
VulDB Temp Score: 5.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Exposure of resource
CWE: CWE-668 / CWE-200 / CWE-284
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

09/22/2023 🔍
09/22/2023 +0 days 🔍
09/22/2023 +0 days 🔍
07/10/2024 +291 days 🔍

Sourcesinfo

Advisory: docs.aws.amazon.com
Status: Not defined
Disputed: 🔍

CVE: CVE-2023-43784 (🔍)
GCVE (CVE): GCVE-0-2023-43784
GCVE (VulDB): GCVE-100-240202

Entryinfo

Created: 09/22/2023 10:03
Updated: 07/10/2024 00:34
Changes: 09/22/2023 10:03 (39), 10/14/2023 14:47 (12), 07/10/2024 00:34 (15)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!