Security readout for executives and security teams
Plain-English summary
This issue can make audit records name the wrong authenticated user. It does not expose data or take systems offline, but it can weaken accountability, investigations, and compliance evidence where Audited logs are trusted.
Executive priority
Address in normal patch cycles unless audit integrity is business-critical. Prioritize sooner for regulated systems, administrator workflows, or environments where audit trails support investigations.
Technical view
Audited 4.0.0 through 5.3.3 has a race condition, classified as CWE-362, where concurrent authenticated activity can cause audit entries to be attributed to another user. CVSS 3.1 is 3.1 with low integrity impact only.
Likely exposure
Exposure is likely limited to applications using the audited package in the affected range and relying on user attribution in audit records. Confirm installed package versions and compare with the vendor advisory.
Exploitation context
The CVSS vector requires network access, low privileges, no user interaction, and high attack complexity. The bundle does not cite public exploitation or CISA KEV listing.
Researcher notes
Evidence supports an authenticated race condition affecting audit-log integrity, not confidentiality or availability. The provided bundle does not establish a specific fixed version, exploit availability, or active exploitation.
Mitigation direction
- Check the Audited vendor advisory for fixed-version guidance.
- Upgrade the audited package if a vendor-supported fixed release is available.
- Treat affected audit attribution as potentially unreliable until remediated.
- Review privileged or compliance-relevant actions during the exposure window.
Validation and detection
- Inventory applications that include the audited package.
- Confirm deployed audited versions against the affected range.
- Review tests or logs for concurrent request attribution issues.
- Verify remediation using vendor advisory criteria after upgrade.
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-362: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-22047 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.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/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:L/UI:N/S:U/C:N/I:L/A:N1.61.4VulnCheckVulnerability scoring details
Base CVSS 3.1 score
3.1LowVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/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://github.com/collectiveidea/audited/security/advisories/GHSA-hjp3-5g2q-7jwwCVE reference, VulnCheck · vendor-advisory
- https://github.com/collectiveidea/audited/issues/601CVE reference, VulnCheck · issue-tracking
- https://github.com/collectiveidea/audited/pull/669CVE reference, VulnCheck · issue-tracking
- https://github.com/collectiveidea/audited/pull/671CVE reference, VulnCheck · issue-tracking
- https://github.com/advisories/GHSA-hjp3-5g2q-7jwwCVE reference, VulnCheck · vendor-advisory
- https://vulncheck.com/advisories/vc-advisory-GHSA-hjp3-5g2q-7jwwCVE reference, VulnCheck · third-party-advisory
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.
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.