What is the severity of REDHAT-BUG-1216035?

The severity of REDHAT-BUG-1216035 is classified as high due to the potential for session hijacking.

How do I fix REDHAT-BUG-1216035?

To fix REDHAT-BUG-1216035, ensure that the _session_id cookie is set with the Secure flag enabled.

What systems are affected by REDHAT-BUG-1216035?

REDHAT-BUG-1216035 affects the Foreman application by The Foreman.

Can REDHAT-BUG-1216035 lead to data breaches?

Yes, REDHAT-BUG-1216035 can lead to data breaches through unauthorized access by attackers via session hijacking.

Is there a workaround for REDHAT-BUG-1216035?

A workaround for REDHAT-BUG-1216035 is to manually set the Secure flag on the _session_id cookie until an official patch is applied.

Vulnerability/
REDHAT-BUG-1216035

medium

28/4/2015

12/5/2023

REDHAT-BUG-1216035

First published: Tue Apr 28 2015(Updated: )

It was reported that the _session_id cookie in Foreman is set without the Secure flag. This may allow an attacker to perform a "session hijacking" attack. Upstream bug: <a href="http://projects.theforeman.org/issues/10275">http://projects.theforeman.org/issues/10275</a> Proposed fix: <a href="https://github.com/theforeman/foreman/pull/2328">https://github.com/theforeman/foreman/pull/2328</a>

Affected Software	Affected Version	How to fix
The Foreman

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of REDHAT-BUG-1216035?
The severity of REDHAT-BUG-1216035 is classified as high due to the potential for session hijacking.
How do I fix REDHAT-BUG-1216035?
To fix REDHAT-BUG-1216035, ensure that the _session_id cookie is set with the Secure flag enabled.
What systems are affected by REDHAT-BUG-1216035?
REDHAT-BUG-1216035 affects the Foreman application by The Foreman.
Can REDHAT-BUG-1216035 lead to data breaches?
Yes, REDHAT-BUG-1216035 can lead to data breaches through unauthorized access by attackers via session hijacking.
Is there a workaround for REDHAT-BUG-1216035?
A workaround for REDHAT-BUG-1216035 is to manually set the Secure flag on the _session_id cookie until an official patch is applied.

agent/type
agent/first-publish-date
agent/last-modified-date
collector/redhat-bugzilla
source/Red Hat
alias/CVE-2015-3155
agent/source
agent/references
agent/severity
agent/description
agent/event
agent/tags
agent/softwarecombine
agent/guess-ai
agent/software-canonical-lookup
agent/software-canonical-lookup-request
vendor/the foreman
canonical/the foreman

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 REDHAT-BUG-1216035?
The severity of REDHAT-BUG-1216035 is classified as high due to the potential for session hijacking.
How do I fix REDHAT-BUG-1216035?
To fix REDHAT-BUG-1216035, ensure that the _session_id cookie is set with the Secure flag enabled.
What systems are affected by REDHAT-BUG-1216035?
REDHAT-BUG-1216035 affects the Foreman application by The Foreman.
Can REDHAT-BUG-1216035 lead to data breaches?
Yes, REDHAT-BUG-1216035 can lead to data breaches through unauthorized access by attackers via session hijacking.
Is there a workaround for REDHAT-BUG-1216035?
A workaround for REDHAT-BUG-1216035 is to manually set the Secure flag on the _session_id cookie until an official patch is applied.