Security readout for executives and security teams
Plain-English summary
CVE-2024-44571 is a high-severity access-control flaw reported in RELY-PCIe versions v22.2.1 through v23.1.0. An authenticated network user could potentially reach functionality they should not, with possible confidentiality, integrity, and availability impact. Public source details are sparse.
Executive priority
Prioritize this for near-term remediation if RELY-PCIe is present in operational or production environments, especially where service interfaces are reachable beyond tightly controlled admin networks.
Technical view
The CVE describes incorrect access control, CWE-284, in the mService function at phpinf.php. CVSS 3.1 is 8.8: network attack vector, low complexity, low privileges required, no user interaction, and high CIA impact. The record does not provide exploit mechanics or a confirmed fix.
Likely exposure
Exposure is most likely where RELY-PCIe v22.2.1 to v23.1.0 is deployed and the affected PHP component is reachable to authenticated users over a network.
Exploitation context
The source bundle does not show CISA KEV listing or cite active exploitation. Treat exploitation status as unconfirmed, not absent, because public technical detail is limited.
Researcher notes
The available record names RELY-PCIe versions and the affected function/path but lacks affected CPEs, vendor/product normalization, exploit details, and remediation specifics. Analysis should remain vendor-guidance driven.
Mitigation direction
Check RELYUM’s vulnerability report and support guidance for fixed versions or workarounds.
Restrict network access to RELY-PCIe administrative or service interfaces.
Limit accounts with access to the affected service surface.
Monitor authentication logs and unusual access to phpinf.php or related service paths.
Validation and detection
Inventory RELY-PCIe deployments and identify versions v22.2.1 through v23.1.0.
Confirm whether phpinf.php and mService functionality are deployed and reachable.
Review access controls for authenticated users with service interface access.
Check vendor advisories for remediation status before closing the finding.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
CWE-284: 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.
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.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.