dbcve.org
Sensitive Information in LogsWeakness · CWE-532

CVE-2025-7371

MEDIUM · 6.8 CVSS v3.1 Published 2025-07-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
Okta On-Premises Provisioning (OPP) agents log certain user data during administrator-initiated password resets. This vulnerability allows an attacker with access to the local servers running OPP agents to retrieve user personal information and temporary passwords created during password reset. You are affected by this vulnerability if the following preconditions are met: Local server running OPP agent with versions >=2.2.1 and <= 2.3.0, and User account has had an administrator-initiated password reset while using the affected versions.

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

Okta On-Premises Provisioning (OPP) agents versions 2.2.1 through 2.3.0 log sensitive user data including personal information and temporary passwords during administrator-initiated password reset operations. An attacker with local server access can read these logs to obtain exposed credentials and PII.

MitigationUpdate OPP agents to a version beyond 2.3.0 when available, audit log files for any unauthorized access, and rotate temporary passwords that may have been exposed during the vulnerable period.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/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. Check OPP agent installed version
    Run the OPP agent version command or check the agent's about/information panel to identify the installed version number
    Affected if The installed version falls between 2.2.1 and 2.3.0 inclusive
  2. Identify log directory location
    Locate the OPP agent log directory - typically found in the agent's installation directory or configured log path
    Affected if Log files exist in the OPP agent log directory
  3. Review logs for password reset events
    Search log files for entries related to password reset operations, looking for patterns containing temporary passwords, new credentials, or user password change events
    Affected if Logs contain password reset entries with exposed credentials or temporary passwords
  4. Check for PII in logs
    Examine log content for personal identifiable information such as usernames, email addresses, or other user identity data during password reset operations
    Affected if Logs contain PII such as user identifiers or personal information during password reset operations

The environment is affected if the OPP agent version is between 2.2.1 and 2.3.0 and password reset operations have been performed, resulting in sensitive data being written to logs accessible locally.

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

Update OPP agents to a version beyond 2.3.0 when available, audit log files for any unauthorized access, and rotate temporary passwords that may have been exposed during the vulnerable period.

Recommended fix Moderate confidence

Version >2.3.0 (contact Okta support or refer to help.okta.com for specific fixed release)

  1. 1. Identify all servers running Okta On-Premises Provisioning (OPP) agents
  2. 2. Check the current OPP agent version on each server
  3. 3. If version is >=2.2.1 and <=2.3.0, plan for upgrade
  4. 4. Coordinate with administrators to schedule maintenance window
  5. 5. Before upgrade, ensure you have backups and can rollback if needed
  6. 6. Upgrade OPP agent to version >2.3.0 (contact Okta support or check help.okta.com for latest stable release)
  7. 7. After upgrade, verify OPP agent is functioning correctly
  8. 8. Review log files from affected servers to determine if they were compromised during the vulnerable period
Caveat Review Okta release notes for any configuration or compatibility changes in newer OPP agent versions

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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