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

CVE-2015-5718 has a CVSS 2.0 base score of 4.0 (Medium). CVSS vector: AV:N/AC:L/Au:S/C:N/I:N/A:P. EPSS exploitation probability: 0.7%.

Is there a public PoC exploit available for CVE-2015-5718?

Yes, a public proof-of-concept exploit is available for CVE-2015-5718. Prioritise patching immediately. EPSS: 0.7%.

Content Gateway CVE-2015-5718

MEDIUM

Buffer Overflow (CWE-119)

2015-08-12 cve@mitre.org

Denial Of Service Buffer Overflow Content Gateway

4.0

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

4.0 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Confidentiality

None

Integrity

None

Availability

Lifecycle Timeline

CVE Published

Aug 12, 2015 - 14:59 cve.org

MEDIUM 4.0

DescriptionCVE.org

Stack-based buffer overflow in the handle_debug_network function in the manager in Websense Content Gateway before 8.0.0 HF02 allows remote administrators to cause a denial of service (crash) via a crafted diagnostic command line request to submit_net_debug.cgi.

AnalysisAI

Stack-based buffer overflow in the handle_debug_network function in the manager in Websense Content Gateway before 8.0.0 HF02 allows remote administrators to cause a denial of service (crash) via a. Rated medium severity (CVSS 4.0), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and 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. Stack-based buffer overflow in the handle_debug_network function in the manager in Websense Content Gateway before 8.0.0 HF02 allows remote administrators to cause a denial of service (crash) via a crafted diagnostic command line request to submit_net_debug.cgi. Affected products include: Websense Content Gateway. Version information: before 8.0.0.

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.