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

CVE-2012-3368 has a CVSS 2.0 base score of 2.6 (Low). CVSS vector: AV:N/AC:H/Au:N/C:P/I:N/A:N. EPSS exploitation probability: 0.4%.

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

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

Is there a patch available for CVE-2012-3368?

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

Dtach CVE-2012-3368

LOW

Numeric Errors (CWE-189)

2012-07-03 secalert@redhat.com

Information Disclosure Dtach

2.6

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

2.6 LOW

AV:N/AC:H/Au:N/C:P/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:H/Au:N/C:P/I:N/A:N

Attack Vector

Network

Attack Complexity

High

Confidentiality

Integrity

None

Availability

None

Lifecycle Timeline

CVE Published

Jul 03, 2012 - 21:55 cve.org

LOW 2.6

DescriptionCVE.org

Integer signedness error in attach.c in dtach 0.8 allows remote attackers to obtain sensitive information from daemon stack memory in opportunistic circumstances by reading application data after an improper connection-close request, as demonstrated by running an IRC client in dtach.

AnalysisAI

Integer signedness error in attach.c in dtach 0.8 allows remote attackers to obtain sensitive information from daemon stack memory in opportunistic circumstances by reading application data after an. Rated low severity (CVSS 2.6), this vulnerability is remotely exploitable. Public exploit code available.

Technical ContextAI

This vulnerability is classified under CWE-189. Integer signedness error in attach.c in dtach 0.8 allows remote attackers to obtain sensitive information from daemon stack memory in opportunistic circumstances by reading application data after an improper connection-close request, as demonstrated by running an IRC client in dtach. Affected products include: Redhat Dtach.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.