CVE-2024-36795
CVE-2024-36795 is a medium-severity vulnerability in Netgear Wnr614 Firmware with a CVSS 3.x base score of 4.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-22.
Key facts
- Severity: Medium (CVSS 3.x base score 4.0)
- EPSS exploit prediction: 0% (27th percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2024-36218
- Weakness: CWE-22
- Affected product: Netgear Wnr614 Firmware
- Published:
- Last modified:
Description
Insecure permissions in Netgear WNR614 JNR1010V2/N300-V1.1.0.54_1.0.1 allows attackers to access URLs and directories embedded within the firmware via unspecified vectors.
Frequently asked questions
- What is CVE-2024-36795?
- Insecure permissions in Netgear WNR614 JNR1010V2/N300-V1.1.0.54_1.0.1 allows attackers to access URLs and directories embedded within the firmware via unspecified vectors.
- How severe is CVE-2024-36795?
- CVE-2024-36795 has a CVSS 3.x base score of 4.0, rated medium severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.
- Is CVE-2024-36795 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (27th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2024-36795?
- CVE-2024-36795 affects Netgear Wnr614 Firmware. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2024-36795?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- Does CVE-2024-36795 have an EU (EUVD) identifier?
- Yes. CVE-2024-36795 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-36218.
- When was CVE-2024-36795 published?
- CVE-2024-36795 was published on 2024-06-06 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:o:netgear:wnr614_firmware:1.1.0.54_1.0.1:*:*:*:*:*:*:*
More vulnerabilities in Netgear Wnr614 Firmware
- CVE-2016-10174 — Critical (CVSS 9.8): The NETGEAR WNR2000v5 router contains a buffer overflow in the hidden_lang_avi parameter when invoking the URL…
- CVE-2024-36790 — High (CVSS 8.8): Netgear WNR614 JNR1010V2/N300-V1.1.0.54_1.0.1 was discovered to store credentials in plaintext.
- CVE-2024-36787 — High (CVSS 8.8): An issue in Netgear WNR614 JNR1010V2 N300-V1.1.0.54_1.0.1 allows attackers to bypass authentication and access the…
- CVE-2017-18791 — High (CVSS 8.8): Certain NETGEAR devices are affected by CSRF. This affects R6050/JR6150 before 1.0.1.7, PR2000 before 1.0.0.17, R6220…
- CVE-2019-20690 — High (CVSS 8.8): Certain NETGEAR devices are affected by authentication bypass. This affects D6200 before 1.1.00.30, D7000 before…
- CVE-2024-36792 — High (CVSS 8.2): An issue in the implementation of the WPS in Netgear WNR614 JNR1010V2/N300-V1.1.0.54_1.0.1 allows attackers to gain…
All CVEs affecting Netgear Wnr614 Firmware →
Other CWE-22 (Path Traversal) vulnerabilities
- CVE-2026-77312 — Critical (CVSS 10.0): Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.8, the earlier CVE-2026-67429…
- CVE-2026-121351 — Critical (CVSS 10.0): Adobe Connect is affected by an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')…
- CVE-2026-121489 — Critical (CVSS 10.0): Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache Juneau. The…
- CVE-2026-122013 — Critical (CVSS 10.0): A vulnerability was detected in Comfast CF-WR632AX 2.6.0.1. Affected by this vulnerability is an unknown functionality…
- CVE-2026-61738 — Critical (CVSS 10.0): SOCFortress CoPilot focuses on providing a single pane of glass for all your security operations needs. Prior to…
- CVE-2026-112690 — Critical (CVSS 10.0): This issue was addressed with improved input validation. This issue is fixed in iOS 26.7.2 and iPadOS 26.7.2, iOS 27.2…