What is the severity of CVE-2011-2532?

CVE-2011-2532 has been classified as a high-severity vulnerability due to its potential to cause denial of service.

How do I fix CVE-2011-2532?

To fix CVE-2011-2532, you need to upgrade Prosody to version 0.8.1 or later.

What type of attack does CVE-2011-2532 enable?

CVE-2011-2532 enables remote attackers to launch denial of service attacks through invalid JSON data.

Which versions of Prosody are affected by CVE-2011-2532?

CVE-2011-2532 affects Prosody version 0.8.0 and earlier versions.

What causes the vulnerability in CVE-2011-2532?

The vulnerability in CVE-2011-2532 is caused by the json.decode function entering an infinite loop when handling truncated or invalid JSON data.

Vulnerability/
CVE-2011-2532

medium

CWE

399

22/6/2011

16/9/2024

CVE-2011-2532

First published: Wed Jun 22 2011(Updated: )

The json.decode function in util/json.lua in Prosody 0.8.x before 0.8.1 might allow remote attackers to cause a denial of service (infinite loop) via invalid JSON data, as demonstrated by truncated data.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Prosody	=0.8.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2011-2532?
CVE-2011-2532 has been classified as a high-severity vulnerability due to its potential to cause denial of service.
How do I fix CVE-2011-2532?
To fix CVE-2011-2532, you need to upgrade Prosody to version 0.8.1 or later.
What type of attack does CVE-2011-2532 enable?
CVE-2011-2532 enables remote attackers to launch denial of service attacks through invalid JSON data.
Which versions of Prosody are affected by CVE-2011-2532?
CVE-2011-2532 affects Prosody version 0.8.0 and earlier versions.
What causes the vulnerability in CVE-2011-2532?
The vulnerability in CVE-2011-2532 is caused by the json.decode function entering an infinite loop when handling truncated or invalid JSON data.

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

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-2011-2532?
CVE-2011-2532 has been classified as a high-severity vulnerability due to its potential to cause denial of service.
How do I fix CVE-2011-2532?
To fix CVE-2011-2532, you need to upgrade Prosody to version 0.8.1 or later.
What type of attack does CVE-2011-2532 enable?
CVE-2011-2532 enables remote attackers to launch denial of service attacks through invalid JSON data.
Which versions of Prosody are affected by CVE-2011-2532?
CVE-2011-2532 affects Prosody version 0.8.0 and earlier versions.
What causes the vulnerability in CVE-2011-2532?
The vulnerability in CVE-2011-2532 is caused by the json.decode function entering an infinite loop when handling truncated or invalid JSON data.

CVE-2011-2532

Remedy

Remedy

Remedy

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2011-2532?

How do I fix CVE-2011-2532?

What type of attack does CVE-2011-2532 enable?

Which versions of Prosody are affected by CVE-2011-2532?

What causes the vulnerability in CVE-2011-2532?

Company

Resources

Contact

Frequently Asked Questions

What is the severity of CVE-2011-2532?

How do I fix CVE-2011-2532?

What type of attack does CVE-2011-2532 enable?

Which versions of Prosody are affected by CVE-2011-2532?

What causes the vulnerability in CVE-2011-2532?