LiveActive security incident?Get immediate response
CVE Record

CVE-2024-55399: 4C Strategies Exonaut before v21.6.2.1-1 was discovered to contain a Server-Side Request Forgery (SSRF).

4C Strategies Exonaut before v21.6.2.1-1 was discovered to contain a Server-Side Request Forgery (SSRF).

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-55399 is an SSRF flaw in 4C Strategies Exonaut before v21.6.2.1-1. An unauthenticated network attacker may be able to make the server issue unintended requests, potentially exposing limited internal data or affecting request integrity. The published severity is medium, not critical.

Executive priority

Treat this as a timely medium-priority remediation item for exposed Exonaut systems. Prioritize internet-facing or broadly reachable deployments because SSRF can bridge external access into internal resources.

Technical view

The CVE maps to CWE-918 SSRF with CVSS 3.1 score 6.5: network reachable, low complexity, no privileges, no user interaction, unchanged scope, low confidentiality and integrity impact, no availability impact. The bundle does not provide endpoint details or confirmed affected CPEs.

Likely exposure

Organizations using 4C Strategies Exonaut versions before v21.6.2.1-1 are the likely exposed population. The source bundle’s affected-product metadata is incomplete, so confirm exposure through asset inventory and vendor records.

Exploitation context

CISA KEV status is false in the bundle, and no cited source confirms active exploitation. A public reference is listed, but the bundle does not establish exploit maturity, real-world use, or attack prevalence.

Researcher notes

The bundle establishes the vulnerability class, product name, version boundary, CVSS vector, and CWE. It does not provide vulnerable routes, proof details, vendor advisory text, CPEs, or confirmed exploitation, so avoid assumptions beyond the CVE record.

Mitigation direction

  • Identify all Exonaut deployments and record exact versions.
  • Upgrade Exonaut to v21.6.2.1-1 or later if vendor guidance confirms the fix.
  • Restrict external access to Exonaut where business requirements allow.
  • Review vendor advisories for configuration-specific mitigations or compensating controls.

Validation and detection

  • Confirm deployed Exonaut versions against the vulnerable pre-v21.6.2.1-1 range.
  • Check whether Exonaut is internet-accessible or reachable by untrusted networks.
  • Review application and egress logs for unusual server-initiated outbound requests.
  • Verify post-upgrade versions and document remediation evidence.
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 · medium confidence lookup

CWE-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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
description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-55399 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-55399Attack 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-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.