dbcve.org
Argus SafetyApplication · Oracle

CVE-2025-21570

MEDIUM · 6.1 CVSS v3.1 Published 2025-01-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Vulnerability in the Oracle Life Sciences Argus Safety product of Oracle Health Sciences Applications (component: Login). The supported version that is affected is 8.2.3. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Life Sciences Argus Safety. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Life Sciences Argus Safety, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Life Sciences Argus Safety accessible data as well as unauthorized read access to a subset of Oracle Life Sciences Argus Safety accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).

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

A vulnerability in the Login component of Oracle Life Sciences Argus Safety 8.2.3 allows unauthenticated attackers via HTTP to gain unauthorized read and write/delete access to a subset of the application's data. The attack requires human interaction from a person other than the attacker, and due to scope change, it may impact additional products beyond the Argus Safety application.

MitigationApply the Oracle security patch for CVE-2025-21570 when available. Until then, restrict network access to the Argus Safety interface and monitor for suspicious login attempts or unauthorized data access patterns.

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
Argus SafetyApplication
Affected:= 8.2.3

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Confirm Argus Safety version
    Locate the installed version of Oracle Life Sciences Argus Safety in the system documentation, application metadata, or about screen. Common paths include the application's bin directory, configuration files, or the Oracle enterprise manager interface.
    Affected if The installed version is exactly 8.2.3
  2. Verify HTTP interface exposure
    Determine if the Argus Safety Login component is accessible via HTTP/HTTPS. Check web server configuration, load balancer settings, or network access controls that expose the application URL.
    Affected if The Login component is exposed to network-accessible HTTP endpoints
  3. Review login access logs
    Examine Argus Safety authentication logs for failed login attempts, unauthorized access patterns, or login attempts from unexpected IP addresses. Check logs under the application's log directory or Oracle Diagnostic Logging location.
    Affected if There are unexplained failed login attempts, unusual login times, or unauthorized access signatures in the logs
  4. Audit data access for unauthorized modifications
    Review application audit logs, data change logs, or database audit trails for read, write, or delete operations performed by unexpected users or outside normal business hours.
    Affected if Data access or modification records exist that cannot be attributed to legitimate users

The environment is affected if Oracle Argus Safety version 8.2.3 is running with the Login component exposed via HTTP, regardless of whether signs of exploitation are found in logs.

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

Apply the Oracle security patch for CVE-2025-21570 when available. Until then, restrict network access to the Argus Safety interface and monitor for suspicious login attempts or unauthorized data access patterns.

Fix this in Argus Safety Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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