Security readout for executives and security teams
Plain-English summary
RELY-PCIe versions v22.2.1 through v23.1.0 may issue sensitive cookies without the Secure flag. In some situations, a browser could send those cookies over unencrypted HTTP, exposing session data to interception. The published severity is low.
Executive priority
Handle as a low-priority but legitimate security hygiene issue. Prioritize sooner for exposed or remotely managed deployments, especially where HTTP remains reachable. It does not indicate integrity or availability impact in the provided CVSS data.
Technical view
The issue is missing Secure cookie attributes in HTTPS sessions. The CVSS 3.1 score is 3.7, with network attack vector, high attack complexity, no privileges, no user interaction, and low confidentiality impact only. The source lists CWE-732 and no concrete CPEs.
Likely exposure
Exposure appears limited to deployments running RELY-PCIe v22.2.1 to v23.1.0 where browsers can make HTTP requests to the same cookie scope. Risk is higher if management traffic crosses untrusted networks. The bundle does not identify specific CPEs or deployment models.
Exploitation context
The source bundle does not indicate active exploitation, and KEV is false. Practical exploitation would depend on conditions that cause sensitive cookies to traverse HTTP, plus an attacker able to observe that traffic. No exploit details are provided in the sources.
Researcher notes
Evidence is narrow: one vendor reference, CVE metadata, no named CPEs, and no cited patch version in the bundle. The title supplies affected RELY-PCIe versions, but the affected product fields are n/a. Avoid assuming broader RELYUM product impact.
Mitigation direction
- Check Relyum guidance for an official fixed version or workaround.
- Upgrade affected RELY-PCIe versions if the vendor provides a corrected release.
- Ensure sensitive cookies are configured with the Secure attribute where supported.
- Disable plain HTTP access or enforce HTTPS-only management access.
- Restrict administrative interfaces to trusted networks.
Validation and detection
- Inventory RELY-PCIe instances and identify versions v22.2.1 through v23.1.0.
- Review HTTPS session cookies for missing Secure attributes.
- Confirm sensitive cookies are not sent during HTTP requests.
- Check vendor advisory updates for fixed versions or mitigation instructions.
- Review logs for unexpected HTTP access to management endpoints.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-732: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-44575 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N2.21.4CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
3.7LowVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.relyum.com/web/support/vulnerability-report/CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Permission Assignment for Critical Resource
Incorrect Permission Assignment for Critical Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.