Skip to content
Systems

CVE-2024-58315

8.5
High
EPSS 0.22%Dec 31, 2025

Unquoted service path in Tosibox Key Service 3.3.0 enables local privilege escalation.

common questions

Is CVE-2024-58315 being exploited?

Not confirmed. CVE-2024-58315 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.22% probability of exploitation in the next 30 days.

How severe is CVE-2024-58315?

CVE-2024-58315 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2024-58315?

Not known from our data. No patch reference has been recorded for CVE-2024-58315, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2024-58315 affect?

CVE-2024-58315 affects Tosibox Key Service 3.3.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2024-58315?

Apply patch when available; fix unquoted service path and limit startup privileges.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Tosibox Key Service 3.3.0
impact

Local non-privileged user can escalate to SYSTEM by abusing the service startup path, enabling code at boot.

action required

Patch when possible

affected versions
Tosibox Oy Tosibox Key Service
  • affected<= 3.3.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free