CVE-2024-10435
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was found in didi Super-Jacoco 1.0. It has been declared as critical. This vulnerability affects unknown code of the file /cov/triggerEnvCov. The manipulation of the argument uuid leads to command injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA command injection vulnerability exists in Didi Super-Jacoco 1.0 where the 'uuid' parameter in the /cov/triggerEnvCov endpoint is not properly sanitized, allowing remote attackers to execute arbitrary OS commands by injecting shell metacharacters.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Didi Super-Jacoco is deployedLocate the Super-Jacoco application files or running process. Check for Java processes named 'super-jacoco' or service directories containing 'super-jacoco' in the application runtime path.Affected if The application is running or installed on the system
-
Verify the Super-Jacoco versionInspect the JAR file, WAR file, or build configuration for the version identifier. Check the application's about page, metadata files (MANIFEST.MF), or startup logs for version information.Affected if The installed version is Super-Jacoco 1.0 (the only affected version listed)
-
Confirm the vulnerable endpoint existsAccess the application's web interface or API documentation. Verify that /cov/triggerEnvCov endpoint is present and accessible. This endpoint typically handles coverage trigger operations.Affected if The /cov/triggerEnvCov endpoint responds to HTTP requests
-
Check network exposure of the serviceReview firewall rules, reverse proxy configurations, and network ACLs to determine if the Super-Jacoco service is exposed to untrusted networks. Use netstat or ss commands to identify listening ports and their bound addresses.Affected if The service is reachable from untrusted network segments or the public internet
A user is affected if Didi Super-Jacoco version 1.0 is installed and the /cov/triggerEnvCov endpoint is network-accessible without proper input sanitization on the uuid parameter.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict network access to the vulnerable endpoint immediately. Apply vendor patch when available. Until patch is available, implement input validation on the uuid parameter to reject shell metacharacters.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10435 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-10435 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data