dbcve.org
Ehrd CtmsApplication · Sun.net

CVE-2024-10438

HIGH · 7.5 CVSS v3.1 Published 2024-10-28
Fix available
A fix is available. Upgrade to 10.14 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
The eHRD CTMS from Sunnet has an Authentication Bypass vulnerability, allowing unauthenticated remote attackers to bypass authentication by satisfying specific conditions in order to access certain functionalities.

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 · moderate confidence

The eHRD CTMS from Sunnet contains an authentication bypass vulnerability that allows unauthenticated remote attackers to bypass the authentication mechanism by satisfying specific, undefined conditions to gain access to certain functionalities within the clinical trial management system.

MitigationApply vendor-supplied patches or updates for eHRD CTMS; if no patch is available, implement compensating controls such as network segmentation, WAF rules, and rigorous access logging until a fix is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ehrd CtmsApplication
Affected:< 10.14

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if eHRD CTMS is installed
    Check your system for the presence of Sun.net eHRD CTMS application. Look for installation directories, services named 'eHRD CTMS' or 'eHRD', or check running processes for CTMS-related executables.
    Affected if eHRD CTMS from Sun.net is present on the system
  2. Check the installed version
    Locate the version information for the eHRD CTMS installation. This may be found in the application itself (typically in About or System Info pages), in installation logs, or in version metadata files within the application directory.
    Affected if The installed version is any version below 10.14 (e.g., 10.13, 10.12, earlier versions)
  3. Verify network accessibility
    Determine if the eHRD CTMS web interface is accessible from network locations. Check firewall rules, network configurations, and determine whether the application port is exposed to untrusted networks.
    Affected if The CTMS interface is reachable from external or untrusted networks without proper network segmentation
  4. Review authentication configuration
    Examine the authentication settings within the CTMS administrative console. Look for authentication-related configuration files or settings that control how user credentials are validated.
    Affected if Authentication mechanisms appear misconfigured, disabled, or allow fallback to unauthenticated states

You are affected if Sun.net eHRD CTMS is installed and the version is below 10.14, especially if the system is network-accessible to untrusted users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 10.14 or later
Fixed in 10.14
Interim mitigation

Apply vendor-supplied patches or updates for eHRD CTMS; if no patch is available, implement compensating controls such as network segmentation, WAF rules, and rigorous access logging until a fix is released.

Recommended fix Moderate confidence

10.14

  1. 1. Identify the current version of eHRD CTMS installed in your environment
  2. 2. If the current version is below 10.14, plan an upgrade to version 10.14 or later
  3. 3. Obtain the upgrade package from the official Sunnet vendor or authorized distribution channel
  4. 4. Before applying the upgrade, perform a complete backup of the current system configuration and data
  5. 5. Apply the upgrade to version 10.14 following Sunnet's documented upgrade procedures
  6. 6. After upgrade completion, verify that the authentication bypass vulnerability is no longer exploitable
  7. 7. Confirm that legitimate authentication is required for accessing protected functionalities

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ehrd Ctms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10438 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-10438 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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