What is the severity of CVE-2005-1730?

CVE-2005-1730 is classified as a high-severity vulnerability due to its potential for remote denial of service attacks.

How do I fix CVE-2005-1730?

To mitigate CVE-2005-1730, it is recommended to update Novell iManager to a version beyond 2.0.2.

What impact does CVE-2005-1730 have on Novell iManager?

CVE-2005-1730 can cause a denial of service in Novell iManager by exploiting the ASN.1 parser.

Who is affected by CVE-2005-1730?

CVE-2005-1730 affects users running Novell iManager version 2.0.2 or earlier.

Is CVE-2005-1730 related to other vulnerabilities?

Yes, CVE-2005-1730 may overlap with vulnerabilities such as CVE-2004-0079 and CVE-2004-0081.

Vulnerability/
CVE-2005-1730

critical

9.3

CWE

NVD-CWE-Other 476

31/12/2005

3/3/2007

7/8/2024

CVE-2005-1730: Null Pointer Dereference

First published: Sat Dec 31 2005(Updated: )

Multiple vulnerabilities in the OpenSSL ASN.1 parser, as used in Novell iManager 2.0.2, allows remote attackers to cause a denial of service (NULL pointer dereference) via crafted packets, as demonstrated by "OpenSSL ASN.1 brute forcer." NOTE: this issue might overlap CVE-2004-0079, CVE-2004-0081, or CVE-2004-0112.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Novell iManager	<=2.0.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2005-1730?
CVE-2005-1730 is classified as a high-severity vulnerability due to its potential for remote denial of service attacks.
How do I fix CVE-2005-1730?
To mitigate CVE-2005-1730, it is recommended to update Novell iManager to a version beyond 2.0.2.
What impact does CVE-2005-1730 have on Novell iManager?
CVE-2005-1730 can cause a denial of service in Novell iManager by exploiting the ASN.1 parser.
Who is affected by CVE-2005-1730?
CVE-2005-1730 affects users running Novell iManager version 2.0.2 or earlier.
Is CVE-2005-1730 related to other vulnerabilities?
Yes, CVE-2005-1730 may overlap with vulnerabilities such as CVE-2004-0079 and CVE-2004-0081.

collector/nvd-historical
collector/nvd-index
agent/references
agent/type
agent/first-publish-date
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/weakness
agent/author
agent/description
agent/tags
agent/event
agent/source
vendor/novell
canonical/novell imanager
version/novell imanager/2.0.2

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-2005-1730?
CVE-2005-1730 is classified as a high-severity vulnerability due to its potential for remote denial of service attacks.
How do I fix CVE-2005-1730?
To mitigate CVE-2005-1730, it is recommended to update Novell iManager to a version beyond 2.0.2.
What impact does CVE-2005-1730 have on Novell iManager?
CVE-2005-1730 can cause a denial of service in Novell iManager by exploiting the ASN.1 parser.
Who is affected by CVE-2005-1730?
CVE-2005-1730 affects users running Novell iManager version 2.0.2 or earlier.
Is CVE-2005-1730 related to other vulnerabilities?
Yes, CVE-2005-1730 may overlap with vulnerabilities such as CVE-2004-0079 and CVE-2004-0081.