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

CVE-2012-2086 has a CVSS 2.0 base score of 7.5 (High). CVSS vector: AV:N/AC:L/Au:N/C:P/I:P/A:P. EPSS exploitation probability: 0.7%.

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

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

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

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

Gajim CVE-2012-2086

HIGH

SQL Injection (CWE-89)

2012-11-23 secalert@redhat.com

SQLi Gajim

7.5

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

Nov 23, 2012 - 20:55 cve.org

HIGH 7.5

DescriptionCVE.org

SQL injection vulnerability in the get_last_conversation_lines function in common/logger.py in Gajim before 0.15 allows remote attackers to execute arbitrary SQL commands via the jig parameter.

AnalysisAI

SQL injection vulnerability in the get_last_conversation_lines function in common/logger.py in Gajim before 0.15 allows remote attackers to execute arbitrary SQL commands via the jig parameter. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified as SQL Injection (CWE-89), which allows attackers to execute arbitrary SQL commands against the database. SQL injection vulnerability in the get_last_conversation_lines function in common/logger.py in Gajim before 0.15 allows remote attackers to execute arbitrary SQL commands via the jig parameter. Affected products include: Gajim. Version information: before 0.15.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Use parameterized queries/prepared statements. Never concatenate user input into SQL. Apply least-privilege database permissions.