PHP-Proxy 5.1.0 helpers.php str_rot_pass cryptographic issues
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
7.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in PHP-Proxy 5.1.0 and classified as critical. Affected by this issue is the function str_rot_pass
of the file vendor/atholn1600/php-proxy/src/helpers.php. The manipulation leads to cryptographic issues.
This vulnerability is handled as CVE-2018-19784. The attack may be launched remotely. There is no exploit available.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability has been found in PHP-Proxy 5.1.0 (Firewall Software) and classified as critical. Affected by this vulnerability is the function str_rot_pass
of the file vendor/atholn1600/php-proxy/src/helpers.php. The manipulation with an unknown input leads to a cryptographic issues vulnerability. The CWE definition for the vulnerability is CWE-310. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
The str_rot_pass function in vendor/atholn1600/php-proxy/src/helpers.php in PHP-Proxy 5.1.0 uses weak cryptography, which makes it easier for attackers to calculate the authorization data needed for local file inclusion.
The bug was discovered 11/30/2018. The weakness was presented 12/01/2018 (Website). It is possible to read the advisory at github.com. This vulnerability is known as CVE-2018-19784 since 11/30/2018. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1600 according to MITRE ATT&CK.
By approaching the search of inurl:vendor/atholn1600/php-proxy/src/helpers.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-127364 for similar entry. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cryptographic issuesCWE: CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
11/30/2018 🔍11/30/2018 🔍
11/30/2018 🔍
12/01/2018 🔍
12/01/2018 🔍
06/12/2023 🔍
Sources
Advisory: 139Status: Not defined
CVE: CVE-2018-19784 (🔍)
GCVE (CVE): GCVE-0-2018-19784
GCVE (VulDB): GCVE-100-127363
See also: 🔍
Entry
Created: 12/01/2018 23:20Updated: 06/12/2023 13:12
Changes: 12/01/2018 23:20 (57), 04/16/2020 16:20 (1), 06/12/2023 13:12 (3)
Complete: 🔍
Cache ID: 216:55F:103
No comments yet. Languages: en.
Please log in to comment.