# CVE-2024-44575: Security feature bypass in n/a

> Attackers can intercept sensitive session cookies sent over HTTP due to missing Secure attributes, potentially leading to session hijacking.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2024
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-w7hj-m8mm-jwmh

## What is CVE-2024-44575?

CVE-2024-44575 is a low-severity vulnerability in n/a, published on 11 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

RELY-PCIe v22.2.1 to v23.1.0 does not set the Secure attribute for sensitive cookies in HTTPS sessions, which could cause the user agent to send those cookies in cleartext over an HTTP session.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2024-44575?

It affects 1 product.


Products: Relyum Rely-Pcie Firmware.

## How do I fix CVE-2024-44575?

No fix has been published for CVE-2024-44575 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-44575 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-47577](https://insights.sbomify.com/CVE-2023-47577/): Missing authorization in n/a (critical 9.8)
- [CVE-2024-44570](https://insights.sbomify.com/CVE-2024-44570/): Code injection in n/a (high 8.8)
- [CVE-2024-44571](https://insights.sbomify.com/CVE-2024-44571/): Missing authorization in n/a (high 8.8)
- [CVE-2024-44572](https://insights.sbomify.com/CVE-2024-44572/): Command injection in n/a (high 8.8)
- [CVE-2024-44574](https://insights.sbomify.com/CVE-2024-44574/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-44575 and fix it if it is affected.

What it is: CVE-2024-44575 is a low-severity vulnerability in n/a, published on 11 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-44575 in the wild and no public exploit code.

Affected product: n/a. 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-2024-44575/ (Markdown: https://insights.sbomify.com/CVE-2024-44575/index.md)
```

## Sources

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

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