dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2025-0813

MEDIUM · 6.8 CVSS v3.1 Published 2025-03-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
No privileges 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
CWE-287: Improper Authentication vulnerability exists that could cause an Authentication Bypass when an unauthorized user without permission rights has physical access to the EPAS-UI computer and is able to reboot the workstation and interrupt the normal boot process.

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

This is an improper authentication vulnerability (CWE-287) in EPAS-UI where an unauthorized user with physical access to the workstation can bypass authentication by rebooting and interrupting the normal boot process. The attacker exploits the boot sequence to gain unauthorized access to the system without proper credentials.

MitigationImplement boot integrity controls including BIOS/UEFI passwords, secure boot mechanisms, and full disk encryption to prevent unauthorized access during the boot process. Additionally, restrict physical access to the workstation.

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
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 EPAS-UI is installed
    Check for EPAS-UI installation by looking for its service processes, binary locations, or installed packages. Common locations include /opt/enterprisedb/products/ or check systemctl for epas-ui or enterprisedb services.
    Affected if EPAS-UI is installed and running on the system - the vulnerability only affects systems with this product present.
  2. Check BIOS/UEFI password protection
    Access the system BIOS or UEFI configuration during boot (typically via F2, F12, Delete key) and verify whether an admin or boot password is set. On Linux, you can also check if /sys/firmware/efi shows EFI boot and review any TPM-related measurements.
    Affected if No BIOS/UEFI password is set - the attacker can interrupt boot and access boot options without credentials.
  3. Verify Secure Boot status
    On Linux systems, check Secure Boot status using 'mokutil --sb-state' or by examining /sys/firmware/efi/efivars/SecureBoot-* if available. On Windows, check via 'msinfo32' looking for Secure Boot State.
    Affected if Secure Boot is disabled or not available - the attacker can modify boot entries or use unauthorized boot media.
  4. Check for full disk encryption
    Verify if the root partition or system drive is encrypted. On Linux, check for LUKS containers with 'cryptsetup luksDump /dev/sdaX' or look for encrypted volume groups via 'lsblk -o NAME,ENCRYPTION' and ' LVM status. On Windows, check BitLocker status via 'manage-bde -status C:'.
    Affected if Full disk encryption is not enabled - an attacker with physical access can read disk contents directly by booting from removable media.
  5. Assess physical access controls
    Document the physical location and accessibility of the workstation. Check if the machine is in a secured area, locked room, or has chassis locks. Verify if unattended systems require additional authentication (screensaver locks, etc.).
    Affected if The workstation is in an unsecured or publicly accessible location where unauthorized individuals can physically interact with the system.

A user is affected if EPAS-UI is installed and the system lacks boot integrity protections (no BIOS/UEFI password, Secure Boot disabled, no full disk encryption) AND the workstation is in a location where unauthorized physical access is possible.

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

Implement boot integrity controls including BIOS/UEFI passwords, secure boot mechanisms, and full disk encryption to prevent unauthorized access during the boot process. Additionally, restrict physical access to the workstation.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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