CVE-2006-0530: Medium severity CA Messaging vulnerability

Published Feb 2, 2006
·
Updated

Computer Associates (CA) Message Queuing (CAM / CAFT) before 1.07 Build 22016 and 1.11 Build 2920, as used in multiple CA products, allows remote attackers to cause a denial of service via spoofed CAM control messages.

Affected Software

136 affected components
CA Messaging=1.07.220.9
CA Messaging=1.11.27.2
CA Messaging=1.11.26.7
CA Messaging=1.11.29.9
CA Messaging=1.07.220.14
CA Messaging=1.11.27.0
CA Messaging=1.07.220.11
CA Messaging=1.07.220.11
CA Messaging=1.11.27.1
CA Messaging=1.11.29.5
CA Messaging=1.11.29.2
CA Messaging=1.11.29.9
CA Messaging=1.11.29.9
CA Messaging=1.11.29.7
CA Messaging=1.11.29.16
CA Messaging=1.11.29.16
CA Messaging=1.07.220.9
CA Messaging=1.11.29.0
CA Messaging=1.11.29.19
CA Messaging=1.11.22
CA Messaging=1.07.220.11
CA Messaging=1.07.220.7
CA Messaging=1.11.26.9
CA Messaging=1.07.220.15
CA Messaging=1.11.29.3
CA Messaging=1.11.29.3
CA Messaging=1.11.29.8
CA Messaging=1.11.29.17
CA Messaging=1.07.220.8
CA Messaging=1.11.29.18
CA Messaging=1.11.29.2
CA Messaging=1.11.29.6
CA Messaging=1.07.220.13
CA Messaging=1.11.29.13
CA Messaging=1.11.29.4
CA Messaging=1.11.29.2
CA Messaging=1.05
CA Messaging=1.11.19.0
CA Messaging=1.11.26.1
CA Messaging=1.07.220.15
CA Messaging=1.11.21
CA Messaging=1.11.29.4
CA Messaging=1.11.19.0
CA Messaging=1.11.29.8
CA Messaging=1.11.27.1
CA Messaging=1.11.29.19
CA Messaging=1.11.29.16
CA Messaging=1.11.23
CA Messaging=1.11.29.17
CA Messaging=1.11.29.15
CA Messaging=1.11.26
CA Messaging=1.07.220.5
CA Messaging=1.11.29.3
CA Messaging=1.11.29.5
CA Messaging=1.07.220.15
CA Messaging=1.11.29.17
CA Messaging=1.11.29.16
CA Messaging=1.11.29.14
CA Messaging=1.11.26.6
CA Messaging=1.11.29.14
CA Messaging=1.11.29.8
CA Messaging=1.07.220.14
CA Messaging=1.07.220.13
CA Messaging=1.07.220.8
CA Messaging=1.11.29.13
CA Messaging=1.11.27.0
CA Messaging=1.07.220.13
CA Messaging=1.07.220.15
CA Messaging=1.11.29.19
CA Messaging=1.05
CA Messaging=1.11.29.4
CA Messaging=1.11.29.15
CA Messaging=1.11.29.15
CA Messaging=1.07.220.3
CA Messaging=1.11.29.15
CA Messaging=1.11.29.3
CA Messaging=1.11.29.9
CA Messaging=1.11.29.16
CA Messaging=1.07.220.15
CA Messaging=1.11.29.13
CA Messaging=1.11.29.15
CA Messaging=1.07.220.5
CA Messaging=1.05
CA Messaging=1.07.220.5
CA Messaging=1.11.18.0
CA Messaging=1.07.220.5
CA Messaging=1.11.24
CA Messaging=1.07.220.14
CA Messaging=1.11.29.14
CA Messaging=1.07.220.4
CA Messaging=1.11.27.3
CA Messaging=1.11.29.8
CA Messaging=1.11.29.14
CA Messaging=1.05
CA Messaging=1.11.29.4
CA Messaging=1.07.220.8
CA Messaging=1.11.29.19
CA Messaging=1.11.29.18
CA Messaging=1.11.29.14
CA Messaging=1.07.220.11
CA Messaging=1.11.29.5
CA Messaging=1.07.210.0
CA Messaging=1.07.220.14
CA Messaging=1.11.29.13
CA Messaging=1.07.220.7
CA Messaging=1.11.29.9
CA Messaging=1.11.29.17
CA Messaging=1.11.29.5
CA Messaging=1.11.29.19
CA Messaging=1.11.29.18
CA Messaging=1.11.27.0
CA Messaging=1.07.220.11
CA Messaging=1.05
CA Messaging=1.11.27.1
CA Messaging=1.11.29.18
CA Messaging=1.07.220.10
CA Messaging=1.11.29.2
CA Messaging=1.11.25
CA Messaging=1.11.29.8
CA Messaging=1.11.28.0
CA Messaging=1.07.220.13
CA Messaging=1.07.220.14
CA Messaging=1.07.220.7
CA Messaging=1.11.27.1
CA Messaging=1.11.26.10
CA Messaging=1.07.220.0
CA Messaging=1.11.26.2
CA Messaging=1.07.220.6
CA Messaging=1.07.210.0
CA Messaging=1.11.26.8
CA Messaging=1.11.29.13
CA Messaging=1.11.29.18
CA Messaging=1.07.220.13
CA Messaging=1.07.220.0
CA Messaging=1.11.29.17
CA Messaging=1.11.29.5

Remediation

Patch Available

http://secunia.com/advisories/18681

Event History

Feb 2, 2006
CVE Published
08:06 PM
Feb 3, 2006
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2006-0530?

CVE-2006-0530 is rated as a medium severity vulnerability due to its potential to cause denial of service conditions.

2

How do I fix CVE-2006-0530?

To fix CVE-2006-0530, you should upgrade to version 1.07 Build 220_16 or later, and version 1.11 Build 29_20 or later of the CA Message Queuing software.

3

What type of attacks can be executed using CVE-2006-0530?

CVE-2006-0530 allows remote attackers to execute denial of service attacks by sending spoofed CAM control messages.

4

Which CA Message Queuing versions are vulnerable to CVE-2006-0530?

Versions prior to 1.07 Build 220_16 and 1.11 Build 29_20 of CA Message Queuing are vulnerable to CVE-2006-0530.

5

Can CVE-2006-0530 be exploited remotely?

Yes, CVE-2006-0530 can be exploited remotely by sending specially crafted CAM control messages.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203