What is the CVSS score of CVE-2014-2962?

CVE-2014-2962 has a CVSS 2.0 base score of 7.8 (High). CVSS vector: AV:N/AC:L/Au:N/C:C/I:N/A:N. EPSS exploitation probability: 88.9%.

Is there a public PoC exploit available for CVE-2014-2962?

Yes, a public proof-of-concept exploit is available for CVE-2014-2962. Prioritise patching immediately. EPSS: 88.9%.

Is there a patch available for CVE-2014-2962?

Yes, a patch is available for CVE-2014-2962. Update the affected software to the latest version immediately.

N150 F9K1009 Firmware CVE-2014-2962

HIGH

Path Traversal (CWE-22)

2014-06-19 cret@cert.org

Path Traversal N150 F9K1009 Firmware N150 F9K1009

7.8

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

7.8 HIGH

AV:N/AC:L/Au:N/C:C/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:L/Au:N/C:C/I:N/A:N

Attack Vector

Network

Attack Complexity

Low

Confidentiality

Integrity

None

Availability

None

Lifecycle Timeline

CVE Published

Jun 19, 2014 - 10:50 cve.org

HIGH 7.8

DescriptionCVE.org

AnalysisAI

Absolute path traversal vulnerability in the webproc cgi module on the Belkin N150 F9K1009 v1 router with firmware before 1.00.08 allows remote attackers to read arbitrary files via a full pathname. Rated high severity (CVSS 7.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and EPSS exploitation probability 88.9%.

Technical ContextAI

This vulnerability is classified as Path Traversal (CWE-22), which allows attackers to access files and directories outside the intended path. Absolute path traversal vulnerability in the webproc cgi module on the Belkin N150 F9K1009 v1 router with firmware before 1.00.08 allows remote attackers to read arbitrary files via a full pathname in the getpage parameter. Affected products include: Belkin N150 F9K1009 Firmware, Belkin N150 F9K1009. Version information: before 1.00.08.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Validate and canonicalize file paths. Use chroot or sandboxing. Reject input containing path separators or '../' sequences.