CVE-2016-3045: Infoleak

Published Feb 1, 2017
·
Updated

IBM Security Access Manager for Web stores sensitive information in URL parameters. This may lead to information disclosure if unauthorized parties have access to the URLs via server logs, referer header or browser history.

Affected Software

16 affected components
IBM Security Access Manager=9.0.0
IBM Security Access Manager=9.0.0.1
IBM Security Access Manager=9.0.1.0
IBM Security Access Manager for Mobile=8.0.0.0
IBM Security Access Manager for Mobile=8.0.0.5
IBM Security Access Manager for Mobile=8.0.1
IBM Security Access Manager for Mobile=8.0.1.2
IBM Security Access Manager for Mobile=8.0.1.3
IBM Security Access Manager for Mobile=8.0.1.4
IBM Security Access Manager for Web=7.0.0
IBM Security Access Manager for Web=8.0.0
IBM Security Access Manager for Web=8.0.1
IBM Security Access Manager for Web=8.0.1.1
IBM Security Access Manager for Web=8.0.1.2
IBM Security Access Manager for Web=8.0.1.3
IBM Security Access Manager for Web=8.0.1.4

Event History

Feb 1, 2017
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
DescriptionWeakness
Data Sourced
via NVD·08:59 PM
RemedyDescriptionSeverityWeaknessAffected Software
Dec 13, 58332
Event
09:35 PM
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-2016-3045?

CVE-2016-3045 is rated as a medium severity vulnerability due to potential information disclosure risks.

2

How do I fix CVE-2016-3045?

To fix CVE-2016-3045, ensure that sensitive information is not transmitted via URL parameters and implement access controls for server logs.

3

What is affected by CVE-2016-3045?

CVE-2016-3045 affects multiple versions of IBM Security Access Manager for Web and IBM Security Access Manager for Mobile.

4

What are the potential risks of CVE-2016-3045?

The potential risks of CVE-2016-3045 include unauthorized access to sensitive information through server logs, referer headers, or browser history.

5

Is there a workaround for CVE-2016-3045?

A possible workaround for CVE-2016-3045 is to avoid using URL parameters for sensitive information and promote secure coding practices.

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