# CVE-2025-34062: OneLogin AD Connector API Credential and Signing Key Exposure

> An attacker with a valid directory token can retrieve sensitive credentials and signing keys from the OneLogin AD Connector API endpoint.

- **Severity:** Medium 5.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jul 2025
- **Updated:** 1 Jul 2025
- **Also known as:** GHSA-mq9j-59r5-qmvh

## What is CVE-2025-34062?

CVE-2025-34062 is a medium-severity vulnerability in OneLogin Active Directory Connector (ADC), published on 1 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-34062?


## How do I fix CVE-2025-34062?

No fix has been published for CVE-2025-34062 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-34062 being exploited?

There is no known exploitation of CVE-2025-34062 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-34062 and fix it if it is affected.

What it is: CVE-2025-34062 is a medium-severity vulnerability in OneLogin Active Directory Connector (ADC), published on 1 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-34062 in the wild and no public exploit code.

Affected product: OneLogin Active Directory Connector (ADC). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-34062/ (Markdown: https://insights.sbomify.com/CVE-2025-34062/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-34062
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-34062
- OSV: https://osv.dev/vulnerability/CVE-2025-34062

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-34062/
Summaries are generated and may contain mistakes; the official description above is the record.