dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-34062

MEDIUM · 5.7 CVSS v4.0 Published 2025-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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 information disclosure vulnerability exists in OneLogin AD Connector versions prior to 6.1.5 via the /api/adc/v4/configuration endpoint. An attacker with access to a valid directory_token—which may be retrievable from host registry keys or improperly secured logs—can retrieve a plaintext response disclosing sensitive credentials. These may include an API key, AWS IAM access and secret keys, and a base64-encoded JWT signing key used in the tenant’s SSO IdP configuration.

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

OneLogin AD Connector versions before 6.1.5 expose sensitive credentials through the /api/adc/v4/configuration endpoint. An attacker possessing a valid directory_token—which may be obtainable from host registry keys or misconfigured logs—can retrieve plaintext API keys, AWS IAM credentials, and base64-encoded JWT signing keys for the tenant's SSO IdP configuration.

MitigationUpgrade OneLogin AD Connector to version 6.1.5 or later. Additionally, secure registry key permissions and audit/log configurations to prevent unauthorized directory_token retrieval.

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
Local
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Verify OneLogin AD Connector version
    Check the installed version of OneLogin AD Connector on the affected host (typically via installer properties, program files metadata, or vendor documentation). Compare it against version 6.1.5.
    Affected if Installed version is earlier than 6.1.5 (e.g., 6.1.4, 6.1.0, etc.)
  2. Locate directory_token in registry
    Examine host registry keys where OneLogin AD Connector stores authentication tokens. Use regedit or PowerShell to search for entries containing 'directory_token' under OneLogin-related keys.
    Affected if A valid directory_token value is present and readable in the registry
  3. Audit logs for directory_token exposure
    Review OneLogin AD Connector logs and system logs (Windows Event Viewer, application log directories) for occurrences of 'directory_token' in plaintext.
    Affected if Logs contain exposed directory_token values
  4. Test configuration endpoint accessibility
    Using a obtained or existing directory_token, attempt a request to the /api/adc/v4/configuration endpoint (e.g., via curl or Invoke-WebRequest with appropriate headers).
    Affected if The endpoint returns plaintext API keys, AWS credentials, or JWT signing keys

Environment is affected if OneLogin AD Connector version is below 6.1.5 AND a directory_token is accessible (via registry, logs, or other means), allowing retrieval of sensitive credentials from the configuration endpoint.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade OneLogin AD Connector to version 6.1.5 or later. Additionally, secure registry key permissions and audit/log configurations to prevent unauthorized directory_token retrieval.

Recommended fix Moderate confidence

OneLogin AD Connector 6.1.5

  1. Obtain OneLogin AD Connector version 6.1.5 from the official OneLogin support portal at support.onelogin.com
  2. Stop the OneLogin AD Connector service on the affected Windows host
  3. Backup the existing OneLogin AD Connector configuration and data directories
  4. Run the installer for version 6.1.5 to perform the upgrade
  5. Follow the on-screen prompts to complete the installation
  6. Start the OneLogin AD Connector service after installation completes
  7. Verify the upgrade was successful by checking the connector version in the OneLogin admin portal or via the service properties
  8. Confirm the /api/adc/v4/configuration endpoint now properly secures sensitive credentials
Caveat Routine upgrade; test in non-production environment first to verify compatibility with existing directory integration configurations

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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