| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Foreman up to 1.8.0. Affected by this vulnerability is an unknown functionality of the component Cookie Handler. Performing a manipulation of the argument _session_id as part of Cookie results in access control. This vulnerability was named CVE-2015-3155. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Foreman up to 1.8.0 (Service Management Software). It has been classified as problematic. This affects an unknown functionality of the component Cookie Handler. The manipulation of the argument _session_id as part of a Cookie leads to a access control vulnerability. CWE is classifying the issue as CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Foreman before 1.8.1 does not set the secure flag for the _session_id cookie in an https session, which makes it easier for remote attackers to capture this cookie by intercepting its transmission within an http session.
The weakness was presented 08/14/2015 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2015-3155 since 04/10/2015. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 85715 (RHEL 7 : Satellite Server (RHSA-2015:1591)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Red Hat Local Security Checks.
Upgrading to version 1.8.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (85715). See VDB-76304, VDB-77249, VDB-77251 and VDB-77254 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 85715
Nessus Name: RHEL 7 : Satellite Server (RHSA-2015:1591)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Foreman 1.8.1
Patch: github.com
Timeline
04/10/2015 🔍08/14/2015 🔍
08/14/2015 🔍
08/15/2015 🔍
06/12/2022 🔍
Sources
Advisory: RHSA-2015:1591Status: Not defined
Confirmation: 🔍
CVE: CVE-2015-3155 (🔍)
GCVE (CVE): GCVE-0-2015-3155
GCVE (VulDB): GCVE-100-77253
See also: 🔍
Entry
Created: 08/15/2015 21:15Updated: 06/12/2022 11:34
Changes: 08/15/2015 21:15 (55), 10/09/2017 09:51 (2), 06/12/2022 11:27 (4), 06/12/2022 11:34 (1)
Complete: 🔍
Cache ID: 216:7FF:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.