Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2024-55415: DevDojo Voyager Compass Path Traversal

Published Jan 30, 2025 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.7Medium · v3.1
EPSS17.6%97th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Thecontrolgroup
IdentifiersCVE-2024-55415CWE-22 · Improper Limitation of a Pathname…

CVE-2024-55415 is a path traversal vulnerability affecting DevDojo Voyager through version 1.8.0. The flaw resides in Voyager's file-management functionality exposed through the /admin/compass endpoint, where attacker-controlled path input can be manipulated to access files outside the intended directory scope. An attacker can use the issue to read or delete files on the underlying filesystem.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can expose sensitive filesystem data and permit unauthorized deletion of files accessible to the Voyager application process. Deletion of application-critical files can disrupt application operation and cause denial of service. The available information characterizes exploitation as network-accessible and identifies remote unauthenticated exploitation; one conflicting CVSS v3 assessment lists low privileges and user interaction as requirements.

Mitigation

If you can’t patch tonight, do this now.

Remove or disable affected Voyager deployments where feasible. Restrict access to administrative functionality, particularly the Compass file-management interface, using network-layer controls, strong authentication, and least-privilege authorization. Run the application under a minimally privileged account and restrict filesystem permissions so the service cannot read or delete sensitive or critical files outside its required storage locations. Monitor for anomalous file-access and deletion activity.

Remediation

Patch, then assume compromise.

No vendor security update or confirmed fixed Voyager version is available in the provided information. Administrators should monitor DevDojo Voyager's official maintenance channels for a security release and upgrade promptly when a validated fix is available. Until then, avoid deploying affected Voyager versions or migrate to an alternative maintained administration package.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
ThecontrolgroupVoyagerapplication
FAQ

Frequently asked questions

Is CVE-2024-55415 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2024-55415 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2024-55415?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2024-55415.
Is there a patch for CVE-2024-55415?
No vendor security update or confirmed fixed Voyager version is available in the provided information. Administrators should monitor DevDojo Voyager's official maintenance channels for a security release and upgrade promptly when a validated fix is available.
What products are affected by CVE-2024-55415?
Thecontrolgroup Voyager.
How severe is CVE-2024-55415?
CVE-2024-55415 has a CVSS v3.1 score of 5.7 (Medium) and an EPSS score of 17.6% (97th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.