| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GRE Protocol and GRE6 Protocol. It has been classified as critical. This affects an unknown part. This manipulation causes improper authentication. The identification of this vulnerability is CVE-2024-7595. It is possible to initiate the attack remotely. There is no exploit available. This vulnerability has a historic impact because of its background and how it was received.
Details
A vulnerability was found in GRE Protocol and GRE6 Protocol (unknown version). It has been declared as critical. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, integrity, and availability.
The advisory is shared at bugzilla.redhat.com. This vulnerability is known as CVE-2024-7595 since 08/07/2024. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/17/2025). Due to its background and reception, this vulnerability has a historic impact.
The vulnerability scanner Nessus provides a plugin with the ID 242166 (Juniper Junos OS Multiple Vulnerabilities (JSA100061)), which helps to determine the existence of the flaw in a target environment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Tenable (242166). Additional details are provided at ispreview.co.uk. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.6
VulDB Base Score: 5.6
VulDB Temp Score: 5.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 242166
Nessus Name: Juniper Junos OS Multiple Vulnerabilities (JSA100061)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/07/2024 🔍01/16/2025 🔍
01/16/2025 🔍
07/17/2025 🔍
Sources
Advisory: bugzilla.redhat.comStatus: Not defined
CVE: CVE-2024-7595 (🔍)
GCVE (CVE): GCVE-0-2024-7595
GCVE (VulDB): GCVE-100-292129
Misc.: 🔍
Entry
Created: 01/16/2025 15:49Updated: 07/17/2025 11:13
Changes: 01/16/2025 15:49 (47), 01/16/2025 15:50 (3), 07/17/2025 11:13 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.