What is the CVSS score of CVE-2015-8083?

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

Espace Firmware CVE-2015-8083

HIGH

Buffer Overflow (CWE-119)

2015-11-19 cve@mitre.org

Denial Of Service Buffer Overflow Huawei Espace Firmware

7.8

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

7.8 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Confidentiality

None

Integrity

None

Availability

Lifecycle Timeline

CVE Published

Nov 19, 2015 - 20:59 cve.org

HIGH 7.8

DescriptionCVE.org

An unspecified module in Huawei eSpace U1910, U1911, U1930, U1960, U1980, and U1981 unified gateways with software before V200R003C00SPC300 does not properly initialize memory when processing timeout messages, which allows remote attackers to cause a denial of service (out-of-bounds memory access and device restart) via unknown vectors.

AnalysisAI

An unspecified module in Huawei eSpace U1910, U1911, U1930, U1960, U1980, and U1981 unified gateways with software before V200R003C00SPC300 does not properly initialize memory when processing timeout. Rated high severity (CVSS 7.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.

Technical ContextAI

This vulnerability is classified as Buffer Overflow (CWE-119), which allows attackers to corrupt memory to execute arbitrary code or crash the application. An unspecified module in Huawei eSpace U1910, U1911, U1930, U1960, U1980, and U1981 unified gateways with software before V200R003C00SPC300 does not properly initialize memory when processing timeout messages, which allows remote attackers to cause a denial of service (out-of-bounds memory access and device restart) via unknown vectors. Affected products include: Huawei Espace Firmware.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Use memory-safe languages or bounds-checking. Enable ASLR, DEP/NX, stack canaries. Use safe string functions.