# CVE-2018-1127: Auth bypass in Red Hat Gluster Storage

> Attackers can replay session tokens after logout to authenticate as the target user in Red Hat Gluster Storage.

- **Severity:** Medium 4.2 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jwq3-h8rx-wcwj, RHSA-2018:2616

## What is CVE-2018-1127?

CVE-2018-1127 is a medium-severity authentication bypass vulnerability in Red Hat Gluster Storage, published on 11 Sep 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Tendrl API in Red Hat Gluster Storage before 3.4.0 does not immediately remove session tokens after a user logs out. Session tokens remain active for a few minutes allowing attackers to replay tokens acquired via sniffing/MITM attacks and authenticate as the target user.

Weakness: CWE-384 (Session Fixation), CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2018-1127?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tendrl-commons` | Red Hat:storage:3.4:na:el7 | All versions | 0:1.6.3-12.el7rhgs |
| `tendrl-gluster-integration` | Red Hat:storage:3.4:na:el7 | All versions | 0:1.6.3-10.el7rhgs |
| `tendrl-node-agent` | Red Hat:storage:3.4:na:el7 | All versions | 0:1.6.3-10.el7rhgs |
| `python-flask` | Red Hat:storage:3.4:wa:el7 | All versions | 1:0.10.1-5.el7rhgs |
| `python-flask-doc` | Red Hat:storage:3.4:wa:el7 | All versions | 1:0.10.1-5.el7rhgs |
| `python-itsdangerous` | Red Hat:storage:3.4:wa:el7 | All versions | 0:0.23-2.el7 |
| `tendrl-ansible` | Red Hat:storage:3.4:wa:el7 | All versions | 0:1.6.3-7.el7rhgs |
| `tendrl-api` | Red Hat:storage:3.4:wa:el7 | All versions | 0:1.6.3-5.el7rhgs |
| `tendrl-api-httpd` | Red Hat:storage:3.4:wa:el7 | All versions | 0:1.6.3-5.el7rhgs |
| `tendrl-commons` | Red Hat:storage:3.4:wa:el7 | All versions | 0:1.6.3-12.el7rhgs |
| `tendrl-grafana-plugins` | Red Hat:storage:3.4:wa:el7 | All versions | 0:1.6.3-11.el7rhgs |
| `tendrl-monitoring-integration` | Red Hat:storage:3.4:wa:el7 | All versions | 0:1.6.3-11.el7rhgs |
| `tendrl-node-agent` | Red Hat:storage:3.4:wa:el7 | All versions | 0:1.6.3-10.el7rhgs |
| `tendrl-notifier` | Red Hat:storage:3.4:wa:el7 | All versions | 0:1.6.3-4.el7rhgs |
| `tendrl-ui` | Red Hat:storage:3.4:wa:el7 | All versions | 0:1.6.3-11.el7rhgs |

Products: Redhat Gluster Storage.

## How do I fix CVE-2018-1127?

Upgrade to a fixed version.

## Is CVE-2018-1127 being exploited?

There is no known exploitation of CVE-2018-1127 in the wild and no public exploit code.

## Other vulnerabilities in Red Hat Gluster Storage

- [CVE-2015-1795](https://insights.sbomify.com/CVE-2015-1795/): Privilege escalation in n/a (high 7.8)
- [CVE-2017-15087](https://insights.sbomify.com/CVE-2017-15087/): Information disclosure in Gluster Storage for RHEL 6 (high 7.5)
- [CVE-2017-15086](https://insights.sbomify.com/CVE-2017-15086/): Other in Gluster Storage for RHEL 6 (high 7.4)
- [CVE-2015-5242](https://insights.sbomify.com/CVE-2015-5242/): Deserialization in n/a (medium 6.0)
- [CVE-2017-15085](https://insights.sbomify.com/CVE-2017-15085/): Information disclosure in Gluster Storage for RHEL 6 (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1127 and fix it if it is affected.

What it is: CVE-2018-1127 is a medium-severity authentication bypass vulnerability in Red Hat Gluster Storage, published on 11 Sep 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-1127 in the wild and no public exploit code.

Affected product: Red Hat Gluster Storage. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-1127/ (Markdown: https://insights.sbomify.com/CVE-2018-1127/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1127
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1127
- OSV: https://osv.dev/vulnerability/CVE-2018-1127

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-1127/
Summaries are generated and may contain mistakes; the official description above is the record.