What is the severity of CVE-2010-1527?

CVE-2010-1527 is classified as a high severity vulnerability due to its potential to allow remote code execution.

How do I fix CVE-2010-1527?

To fix CVE-2010-1527, update to Novell iPrint Client version 5.44 or later.

What platforms are affected by CVE-2010-1527?

CVE-2010-1527 affects Novell iPrint Client versions up to and including 5.42, as well as versions 4.26 to 5.40.

What type of attack does CVE-2010-1527 enable?

CVE-2010-1527 enables remote attackers to execute arbitrary code on affected systems.

Is there a workaround for CVE-2010-1527 if I cannot update?

There is no known workaround for CVE-2010-1527, so updating to a fixed version is recommended.

Vulnerability/
CVE-2010-1527

critical

9.3

CWE

119

23/8/2010

7/8/2024

CVE-2010-1527: Buffer Overflow

First published: Mon Aug 23 2010(Updated: )

Stack-based buffer overflow in Novell iPrint Client before 5.44 allows remote attackers to execute arbitrary code via a long call-back-url parameter in an op-client-interface-version action.

Credit: PSIRT-CNA@flexerasoftware.com

Affected Software	Affected Version	How to fix
Novell Iprint	<=5.42
Novell Iprint	=4.26
Novell Iprint	=4.27
Novell Iprint	=4.28
Novell Iprint	=4.30
Novell Iprint	=4.32
Novell Iprint	=4.34
Novell Iprint	=4.36
Novell Iprint	=4.38
Novell Iprint	=5.04
Novell Iprint	=5.12
Novell Iprint	=5.20b
Novell Iprint	=5.30
Novell Iprint	=5.32
Novell Iprint	=5.40

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2010-1527?
CVE-2010-1527 is classified as a high severity vulnerability due to its potential to allow remote code execution.
How do I fix CVE-2010-1527?
To fix CVE-2010-1527, update to Novell iPrint Client version 5.44 or later.
What platforms are affected by CVE-2010-1527?
CVE-2010-1527 affects Novell iPrint Client versions up to and including 5.42, as well as versions 4.26 to 5.40.
What type of attack does CVE-2010-1527 enable?
CVE-2010-1527 enables remote attackers to execute arbitrary code on affected systems.
Is there a workaround for CVE-2010-1527 if I cannot update?
There is no known workaround for CVE-2010-1527, so updating to a fixed version is recommended.

collector/nvd-index
collector/nvd-historical
agent/softwarecombine
agent/references
agent/type
collector/mitre-cve
source/MITRE
agent/author
agent/severity
agent/last-modified-date
agent/weakness
agent/tags
agent/description
agent/first-publish-date
agent/event
agent/source
vendor/novell
canonical/novell iprint
version/novell iprint/5.42
version/novell iprint/4.26
version/novell iprint/4.27
version/novell iprint/4.28
version/novell iprint/4.30
version/novell iprint/4.32
version/novell iprint/4.34
version/novell iprint/4.36
version/novell iprint/4.38
version/novell iprint/5.04
version/novell iprint/5.12
version/novell iprint/5.20b
version/novell iprint/5.30
version/novell iprint/5.32
version/novell iprint/5.40

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-2010-1527?
CVE-2010-1527 is classified as a high severity vulnerability due to its potential to allow remote code execution.
How do I fix CVE-2010-1527?
To fix CVE-2010-1527, update to Novell iPrint Client version 5.44 or later.
What platforms are affected by CVE-2010-1527?
CVE-2010-1527 affects Novell iPrint Client versions up to and including 5.42, as well as versions 4.26 to 5.40.
What type of attack does CVE-2010-1527 enable?
CVE-2010-1527 enables remote attackers to execute arbitrary code on affected systems.
Is there a workaround for CVE-2010-1527 if I cannot update?
There is no known workaround for CVE-2010-1527, so updating to a fixed version is recommended.