What is the severity of CVE-2014-0905?

The severity of CVE-2014-0905 is considered medium due to the potential for remote attackers to intercept sensitive cookie data.

How do I fix CVE-2014-0905?

To fix CVE-2014-0905, configure the application to set the secure flag on the LTPA cookie to ensure it is only transmitted over HTTPS connections.

Which versions of IBM InfoSphere BigInsights are affected by CVE-2014-0905?

CVE-2014-0905 affects IBM InfoSphere BigInsights versions 2.0.0.0, 2.1.0.0, 2.1.1.0, and 2.1.2.0.

Can CVE-2014-0905 lead to data breaches?

Yes, CVE-2014-0905 can potentially lead to data breaches if attackers successfully intercept LTPA cookies.

Is there a workaround for CVE-2014-0905?

A potential workaround for CVE-2014-0905 is to utilize additional layers of encryption for cookie transmission in your application.

Vulnerability/
CVE-2014-0905

low

2.9

CWE

264

17/8/2014

6/8/2024

CVE-2014-0905

First published: Sun Aug 17 2014(Updated: )

IBM InfoSphere BigInsights 2.0 through 2.1.2 does not set the secure flag for the LTPA cookie in an https session, which makes it easier for remote attackers to capture this cookie by intercepting its transmission within an http session.

Credit: psirt@us.ibm.com

Affected Software	Affected Version	How to fix
IBM InfoSphere BigInsights	=2.0.0.0
IBM InfoSphere BigInsights	=2.1.0.0
IBM InfoSphere BigInsights	=2.1.1.0
IBM InfoSphere BigInsights	=2.1.2.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2014-0905?
The severity of CVE-2014-0905 is considered medium due to the potential for remote attackers to intercept sensitive cookie data.
How do I fix CVE-2014-0905?
To fix CVE-2014-0905, configure the application to set the secure flag on the LTPA cookie to ensure it is only transmitted over HTTPS connections.
Which versions of IBM InfoSphere BigInsights are affected by CVE-2014-0905?
CVE-2014-0905 affects IBM InfoSphere BigInsights versions 2.0.0.0, 2.1.0.0, 2.1.1.0, and 2.1.2.0.
Can CVE-2014-0905 lead to data breaches?
Yes, CVE-2014-0905 can potentially lead to data breaches if attackers successfully intercept LTPA cookies.
Is there a workaround for CVE-2014-0905?
A potential workaround for CVE-2014-0905 is to utilize additional layers of encryption for cookie transmission in your application.

collector/nvd-index
agent/softwarecombine
agent/type
agent/references
collector/mitre-cve
source/MITRE
agent/weakness
agent/last-modified-date
agent/severity
agent/author
agent/tags
agent/first-publish-date
agent/description
agent/event
agent/source
vendor/ibm
canonical/ibm infosphere biginsights
version/ibm infosphere biginsights/2.0.0.0
version/ibm infosphere biginsights/2.1.0.0
version/ibm infosphere biginsights/2.1.1.0
version/ibm infosphere biginsights/2.1.2.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-2014-0905?
The severity of CVE-2014-0905 is considered medium due to the potential for remote attackers to intercept sensitive cookie data.
How do I fix CVE-2014-0905?
To fix CVE-2014-0905, configure the application to set the secure flag on the LTPA cookie to ensure it is only transmitted over HTTPS connections.
Which versions of IBM InfoSphere BigInsights are affected by CVE-2014-0905?
CVE-2014-0905 affects IBM InfoSphere BigInsights versions 2.0.0.0, 2.1.0.0, 2.1.1.0, and 2.1.2.0.
Can CVE-2014-0905 lead to data breaches?
Yes, CVE-2014-0905 can potentially lead to data breaches if attackers successfully intercept LTPA cookies.
Is there a workaround for CVE-2014-0905?
A potential workaround for CVE-2014-0905 is to utilize additional layers of encryption for cookie transmission in your application.