What is the CVSS score of CVE-2012-4335?

CVE-2012-4335 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: 12.2%.

Is there a public PoC exploit available for CVE-2012-4335?

Yes, a public proof-of-concept exploit is available for CVE-2012-4335. Prioritise patching immediately. EPSS: 12.2%.

Net I Viewer CVE-2012-4335

HIGH

Buffer Overflow (CWE-119)

2012-08-14 cve@mitre.org

Buffer Overflow Samsung Denial Of Service Net I Viewer

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

Aug 14, 2012 - 22:55 cve.org

HIGH 7.8

DescriptionCVE.org

Samsung NET-i viewer 1.37.120316 allows remote attackers to cause a denial of service (infinite loop) via a negative size value in a TCP request to (1) NiwMasterService or (2) NiwStorageService. NOTE: some of these details are obtained from third party information.

AnalysisAI

Samsung NET-i viewer 1.37.120316 allows remote attackers to cause a denial of service (infinite loop) via a negative size value in a TCP request to (1) NiwMasterService or (2) NiwStorageService. Rated high severity (CVSS 7.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and EPSS exploitation probability 12.2%.

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. Samsung NET-i viewer 1.37.120316 allows remote attackers to cause a denial of service (infinite loop) via a negative size value in a TCP request to (1) NiwMasterService or (2) NiwStorageService. NOTE: some of these details are obtained from third party information. Affected products include: Samsung Net-I Viewer.

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.