didi CVE Vulnerabilities & Metrics

Focus on didi vulnerabilities and metrics.

Last updated: 08 Mar 2025, 23:25 UTC

About didi Security Exposure

This page consolidates all known Common Vulnerabilities and Exposures (CVEs) associated with didi. We track both calendar-based metrics (using fixed periods) and rolling metrics (using gliding windows) to give you a comprehensive view of security trends and risk evolution. Use these insights to assess risk and plan your patching strategy.

For a broader perspective on cybersecurity threats, explore the comprehensive list of CVEs by vendor and product. Stay updated on critical vulnerabilities affecting major software and hardware providers.

Global CVE Overview

Total didi CVEs: 1
Earliest CVE date: 06 Nov 2024, 16:15 UTC
Latest CVE date: 06 Nov 2024, 16:15 UTC

Latest CVE reference: CVE-2024-10919

Rolling Stats

30-day Count (Rolling): 0
365-day Count (Rolling): 1

Calendar-based Variation

Calendar-based Variation compares a fixed calendar period (e.g., this month versus the same month last year), while Rolling Growth Rate uses a continuous window (e.g., last 30 days versus the previous 30 days) to capture trends independent of calendar boundaries.

Variations & Growth

Month Variation (Calendar): 0%
Year Variation (Calendar): 0%

Month Growth Rate (30-day Rolling): 0.0%
Year Growth Rate (365-day Rolling): 0.0%

Monthly CVE Trends (current vs previous Year)

Annual CVE Trends (Last 20 Years)

Critical didi CVEs (CVSS ≥ 9) Over 20 Years

CVSS Stats

Average CVSS: 6.5

Max CVSS: 6.5

Critical CVEs (≥9): 0

CVSS Range vs. Count

Range Count
0.0-3.9 0
4.0-6.9 1
7.0-8.9 0
9.0-10.0 0

CVSS Distribution Chart

Top 5 Highest CVSS didi CVEs

These are the five CVEs with the highest CVSS scores for didi, sorted by severity first and recency.

All CVEs for didi

CVE-2024-10919 didi vulnerability CVSS: 6.5 06 Nov 2024, 16:15 UTC

A vulnerability has been found in didi Super-Jacoco 1.0 and classified as critical. Affected by this vulnerability is an unknown functionality of the file /cov/triggerUnitCover. The manipulation of the argument uuid leads to os command injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.