dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-39344

HIGH · 8.1 CVSS v3.1 Published 2024-08-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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
An issue was discovered in the Docusign API package 8.142.14 for Salesforce. The Apttus_DocuApi__DocusignAuthentication__mdt object is installed via the marketplace from this package and stores some configuration information in a manner that could be compromised. With the default settings when installed for all users, the object can be accessible and (via its fields) could disclose some keys. These disclosed components can be combined to create a valid session via the Docusign API. This will generally lead to a complete compromise of the Docusign account because the session is for an administrator service account and may have permission to re-authenticate as specific users with the same authorization flow.

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 confidence

The Docusign API package 8.142.14 for Salesforce installs the Apttus_DocuApi__DocusignAuthentication__mdt custom metadata type with default permissions allowing all users read access. This exposes sensitive configuration fields containing API keys/secrets that can be extracted and combined to forge valid Docusign API administrator sessions, resulting in complete Docusign account compromise including the ability to re-authenticate as other users.

MitigationImmediately restrict permissions on the Apttus_DocuApi__DocusignAuthentication__mdt custom metadata type to authorized administrators only, rotate all exposed Docusign API credentials, and audit logs for any unauthorized session activity.

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
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 installed Docusign API package version
    Navigate to Salesforce Setup > Installed Packages (or use SOQL: SELECT Id, Name, VersionNumber FROM SubscriberPackage WHERE Name = 'DocuSign API' or NamespacePrefix = 'Apttus_DocuApi'). Verify the version number is 8.142.14.
    Affected if The installed version matches 8.142.14 exactly.
  2. Locate the vulnerable custom metadata type
    In Salesforce Setup, go to Custom Metadata Types and find 'Apttus_DocuApi__DocusignAuthentication__mdt' (or search for 'DocusignAuthentication'). Confirm this metadata type exists in the org.
    Affected if The Apttus_DocuApi__DocusignAuthentication__mdt custom metadata type is present in the org.
  3. Check profile/permission set permissions on the metadata type
    Navigate to the custom metadata type > Manage Records or view its profile/permission set assignments. Check the Field-Level Security or metadata type access for standard user profiles. Alternatively, query PermissionSetAssignment joined with CustomPermission for profiles assigned to the metadata type.
    Affected if Any standard user profile (non-admin) has Read access granted to this custom metadata type.
  4. Inspect the sensitive fields for exposure
    Open the custom metadata type records and view the fields. Look for fields containing names like 'APIKey', 'APISecret', 'ClientSecret', 'Password', 'Token', or similar credential-type fields. Check Field-Level Security to see if 'Read' is enabled for all users.
    Affected if API key, secret, or token fields are visible to all users through the metadata records.
  5. Verify API credentials are accessible to non-admin users
    As a test, log in as a non-administrative user (or use a permission set that removes admin access) and attempt to view the Apttus_DocuApi__DocusignAuthentication__mdt records. Alternatively, query using a standard user context: SELECT Apttus_DocuApi__API_Key__c, Apttus_DocuApi__API_Secret__c FROM Apttus_DocuApi__DocusignAuthentication__mdt
    Affected if A standard user can query and retrieve the Docusign API credentials from the custom metadata.

Your environment is affected if the Docusign API package version 8.142.14 is installed AND the Apttus_DocuApi__DocusignAuthentication__mdt custom metadata type grants Read access to non-administrative users, allowing standard users to extract sensitive API credentials.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately restrict permissions on the Apttus_DocuApi__DocusignAuthentication__mdt custom metadata type to authorized administrators only, rotate all exposed Docusign API credentials, and audit logs for any unauthorized session activity.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-39344 — 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-39344 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