Enphase Envoy R3.*.* Service Port 8888 credentials management

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.
5.9$0-$5k0.00

Summaryinfo

A vulnerability marked as critical has been reported in Enphase Envoy R3.*.*. Affected is an unknown function of the component Service Port 8888. Performing a manipulation results in credentials management. This vulnerability is identified as CVE-2019-7676. The attack can be initiated remotely. There is not any exploit available. It is suggested to use restrictive firewalling.

Detailsinfo

A vulnerability, which was classified as critical, was found in Enphase Envoy R3.*.*. This affects an unknown code of the component Service Port 8888. The manipulation with an unknown input leads to a credentials management vulnerability. CWE is classifying the issue as CWE-255. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

A weak password vulnerability was discovered in Enphase Envoy R3.*.*. One can login via TCP port 8888 with the admin password for the admin account.

The bug was discovered 02/09/2019. The weakness was released 02/09/2019. This vulnerability is uniquely identified as CVE-2019-7676 since 02/09/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. A authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1552 for this issue.

It is possible to mitigate the weakness by firewalling tcp/8888.

Entries connected to this vulnerability are available at VDB-130703 and VDB-130702. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.9
VulDB Meta Temp Score: 5.9

VulDB Base Score: 4.7
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.2
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Credentials management
CWE: CWE-255
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: Firewall
Status: 🔍

0-Day Time: 🔍

Firewalling: 🔍

Timelineinfo

02/09/2019 🔍
02/09/2019 +0 days 🔍
02/09/2019 +0 days 🔍
02/10/2019 +1 days 🔍
07/09/2023 +1610 days 🔍

Sourcesinfo

Advisory: github.com
Status: Not defined

CVE: CVE-2019-7676 (🔍)
GCVE (CVE): GCVE-0-2019-7676
GCVE (VulDB): GCVE-100-130701
See also: 🔍

Entryinfo

Created: 02/10/2019 10:24
Updated: 07/09/2023 09:15
Changes: 02/10/2019 10:24 (56), 05/09/2020 16:15 (1), 07/09/2023 09:15 (4)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!