What is the severity of CVE-2012-6696?

CVE-2012-6696 is classified as a medium-severity vulnerability that affects the handling of unsigned integers in InspIRCd.

How do I fix CVE-2012-6696?

To fix CVE-2012-6696, upgrade InspIRCd to version 2.0.7 or later which contains the necessary fixes.

What software is affected by CVE-2012-6696?

CVE-2012-6696 affects InspIRCd versions prior to 2.0.7, specifically including versions up to 2.0.5.

What is the cause of CVE-2012-6696?

CVE-2012-6696 exists due to an incomplete fix for an earlier vulnerability, CVE-2012-1836, leading to improper handling of unsigned integers.

When was CVE-2012-6696 discovered?

CVE-2012-6696 was discovered in 2012 and pertains to vulnerabilities found in prior versions of InspIRCd.

Vulnerability/
CVE-2012-6696

critical

9.8

CWE

25/9/2017

6/8/2024

CVE-2012-6696: Input Validation

First published: Mon Sep 25 2017(Updated: )

inspircd in Debian before 2.0.7 does not properly handle unsigned integers. NOTE: This vulnerability exists because of an incomplete fix to CVE-2012-1836.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
InspIRCd	<=2.0.5

Remedy

https://github.com/inspircd/inspircd/commit/ed28c1ba666b39581adb860bf51cdde43c84cc89

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2012-6696?
CVE-2012-6696 is classified as a medium-severity vulnerability that affects the handling of unsigned integers in InspIRCd.
How do I fix CVE-2012-6696?
To fix CVE-2012-6696, upgrade InspIRCd to version 2.0.7 or later which contains the necessary fixes.
What software is affected by CVE-2012-6696?
CVE-2012-6696 affects InspIRCd versions prior to 2.0.7, specifically including versions up to 2.0.5.
What is the cause of CVE-2012-6696?
CVE-2012-6696 exists due to an incomplete fix for an earlier vulnerability, CVE-2012-1836, leading to improper handling of unsigned integers.
When was CVE-2012-6696 discovered?
CVE-2012-6696 was discovered in 2012 and pertains to vulnerabilities found in prior versions of InspIRCd.

agent/type
collector/mitre-cve
source/MITRE
agent/severity
agent/weakness
agent/last-modified-date
agent/remedy
agent/references
agent/author
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
agent/softwarecombine
collector/nvd-index
agent/software-canonical-lookup-request
vendor/inspircd
canonical/inspircd
version/inspircd/2.0.5

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2012-6696?
CVE-2012-6696 is classified as a medium-severity vulnerability that affects the handling of unsigned integers in InspIRCd.
How do I fix CVE-2012-6696?
To fix CVE-2012-6696, upgrade InspIRCd to version 2.0.7 or later which contains the necessary fixes.
What software is affected by CVE-2012-6696?
CVE-2012-6696 affects InspIRCd versions prior to 2.0.7, specifically including versions up to 2.0.5.
What is the cause of CVE-2012-6696?
CVE-2012-6696 exists due to an incomplete fix for an earlier vulnerability, CVE-2012-1836, leading to improper handling of unsigned integers.
When was CVE-2012-6696 discovered?
CVE-2012-6696 was discovered in 2012 and pertains to vulnerabilities found in prior versions of InspIRCd.