dbcve.org
OpenedgeWeb browser · Progress

CVE-2024-1403

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-27
Fix available
A fix is available. Upgrade to 11.7.19 / 12.2.14 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
In OpenEdge Authentication Gateway and AdminServer prior to 11.7.19, 12.2.14, 12.8.1 on all platforms supported by the OpenEdge product, an authentication bypass vulnerability has been identified.  The vulnerability is a bypass to authentication based on a failure to properly handle username and password. Certain unexpected content passed into the credentials can lead to unauthorized access without proper authentication.  

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

OpenEdge Authentication Gateway and AdminServer fail to properly validate credentials, allowing authentication bypass when certain unexpected content is passed in the username or password fields. An attacker can gain unauthorized access without valid credentials.

MitigationUpgrade OpenEdge Authentication Gateway and AdminServer to version 11.7.19, 12.2.14, or 12.8.1 or later to remediate the vulnerability.

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
OpenedgeWeb browser
Affected:< 11.7.19>= 11.8, < 12.2.14>= 12.3, < 12.8.1

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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. Identify installed OpenEdge version
    Run 'proversion' command or check the OpenEdge installation directory for version file. On Windows, check registry under HKLM\Software\Progress\OpenEdge\Version. On Unix/Linux, check $DLC/version or /opt/dlc/version
    Affected if The installed version falls into any of these ranges: < 11.7.19, >= 11.8 and < 12.2.14, or >= 12.3 and < 12.8.1
  2. Determine if Authentication Gateway is deployed
    Check if the Authentication Gateway component is installed and configured. Look for 'oeag' process running, or check for Authentication Gateway configuration files in the OpenEdge install directory under /etc or /properties
    Affected if Authentication Gateway is installed and running on an affected OpenEdge version
  3. Determine if AdminServer is deployed
    Check if the AdminServer (adminsrv) process is running. On Windows, check Windows Services for 'OpenEdge AdminServer'. On Unix/Linux, run 'ps -ef | grep admin' or check for admin server PID files
    Affected if AdminServer is installed and running on an affected OpenEdge version
  4. Verify credential validation behavior
    Attempt a login with unexpected content in username or password fields (e.g., special characters or format strings) to the Authentication Gateway or AdminServer login interface. Review authentication logs in $DLC/servers/oeag/logs or $DLC/servers/pas/admin/logs
    Affected if Authentication succeeds with invalid/malformed credentials, indicating the bypass is present

The environment is affected if OpenEdge Authentication Gateway or AdminServer is running a version in the affected ranges (< 11.7.19, 11.8-12.2.13, or 12.3-12.8.0) and accepts authentication with malformed credentials.

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
Upgrade available Upgrade to 11.7.19 / 12.2.14 / 12.8.1 or later
Fixed in 11.7.1912.2.1412.8.1
Interim mitigation

Upgrade OpenEdge Authentication Gateway and AdminServer to version 11.7.19, 12.2.14, or 12.8.1 or later to remediate the vulnerability.

Recommended fix High confidence

Upgrade to 11.7.19 (for 11.x users), 12.2.14 (for 12.2.x users), or 12.8.1 or later (for 12.3+ users)

  1. 1. Identify the currently installed OpenEdge version using 'proversion' command or checking the installation directory
  2. 2. Determine which upgrade path applies based on current version (11.x, 12.2.x, or 12.3+)
  3. 3. Download the appropriate fixed version from www.progress.com or the Progress Customer Portal
  4. 4. Review the OpenEdge Installation Guide for your platform for pre-upgrade requirements
  5. 5. Create a full backup of the current OpenEdge installation including configuration files, databases, and the OpenEdge repository
  6. 6. Stop all OpenEdge services (AdminServer, Authentication Gateway, and all OpenEdge database servers) before upgrading
  7. 7. Run the installer for the chosen fixed version (11.7.19, 12.2.14, or 12.8.1 or later)
  8. 8. Follow the installation wizard, selecting 'Upgrade' option when prompted
Caveat Review OpenEdge 12.x release notes for any breaking changes between major versions; test applications thoroughly after upgrade as minor version jumps may include behavioral changes

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

Fix this in Openedge Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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