LiveActive security incident?Get immediate response
CVE Record

CVE-2024-55398: 4C Strategies Exonaut before v22.4 was discovered to contain insecure permissions.

4C Strategies Exonaut before v22.4 was discovered to contain insecure permissions.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-55398 describes insecure permissions in 4C Strategies Exonaut before v22.4. A network attacker needs no credentials or user interaction, but the reported impact is limited to low confidentiality and integrity loss, with no availability impact. Business urgency is moderate unless Exonaut is internet-facing or handles sensitive operational data.

Executive priority

Treat as a moderate-priority exposure issue. Prioritize faster action where Exonaut supports emergency, continuity, defense, or sensitive operational planning, or where the system is reachable from untrusted networks.

Technical view

The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N, score 6.5. The weakness is CWE-276, incorrect default or insecure permissions. Public metadata does not provide detailed affected CPEs, exploit mechanics, or vendor remediation notes beyond the version boundary of Exonaut before v22.4.

Likely exposure

Exposure appears limited to organizations running 4C Strategies Exonaut versions before v22.4. The source bundle does not identify CPEs, deployment modes, or specific components, so asset validation must come from internal inventory and vendor records.

Exploitation context

The source bundle does not show CISA KEV listing or other cited evidence of active exploitation. The CVSS vector indicates remote, unauthenticated reachability with low complexity, but no public source here supports confirmed exploitation in the wild.

Researcher notes

Public detail is sparse. The useful facts are the version boundary, CWE-276 classification, and CVSS vector. Avoid assuming a specific permission object, endpoint, or exploit path without the referenced advisory or vendor confirmation.

Mitigation direction

  • Identify all Exonaut deployments and confirm exact versions.
  • Upgrade to Exonaut v22.4 or later if vendor guidance confirms remediation.
  • Review vendor advisories for official fixes, mitigations, and configuration guidance.
  • Restrict network access to Exonaut administration and sensitive interfaces.
  • Review application permissions for overly broad default or inherited access.

Validation and detection

  • Check inventory for any Exonaut version earlier than v22.4.
  • Confirm whether Exonaut is internet-facing or reachable by untrusted networks.
  • Review role, file, and object permissions for unintended broad access.
  • Validate remediation against vendor guidance, not assumptions from CVE metadata.
  • Monitor access logs for unusual unauthenticated or low-privilege activity.
Prepared
Confidence
medium
Sources
3

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 · low confidence lookup

CWE-276: 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 lookup
cve · low confidence lookup

CVE-2024-55398 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Official CVE source material

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.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N3.92.5CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2024-55398Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-276 · source CWE mapping

Incorrect Default Permissions

Incorrect Default Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.