dbcve.org
OpenedgeWeb browser · Progress

CVE-2023-40051

CRITICAL · 9.9 CVSS v3.1 Published 2024-01-18
Fix available
A fix is available. Upgrade to 11.7.18 / 12.2.13 or later.
See remediation →
100/100
Remediation priority · Urgent
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
This issue affects Progress Application Server (PAS) for OpenEdge in versions 11.7 prior to 11.7.18, 12.2 prior to 12.2.13, and innovation releases prior to 12.8.0. An attacker can formulate a request for a WEB transport that allows unintended file uploads to a server directory path on the system running PASOE. If the upload contains a payload that can further exploit the server or its network, the launch of a larger scale attack may be possible.

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

A file upload vulnerability in Progress Application Server (PAS) for OpenEdge allows attackers to upload files to arbitrary server directory paths via specially crafted WEB transport requests. This occurs due to insufficient validation of the upload destination path, enabling unauthenticated remote attackers to write files to the server filesystem.

MitigationUpgrade PAS for OpenEdge to version 11.7.18, 12.2.13, 12.8.0 or later. If immediate patching is not feasible, implement network segmentation to restrict access to PASOE instances and deploy WAF rules to detect and block anomalous file upload requests.

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, < 11.7.18>= 12.2, < 12.2.13
Openedge InnovationWeb browser
Affected:< 12.8.0

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 if Progress OpenEdge PAS is installed
    Look for the Progress OpenEdge installation directory, typically under /opt/progress or C:\Progress on Linux/Windows. Check for the 'pasoe' subdirectory which contains the PAS for OpenEdge instance.
    Affected if Progress OpenEdge PAS is found on the system
  2. Determine the installed PAS for OpenEdge version
    Locate the version file or check the product version using the 'openedge' command with version flags, or inspect the PASOE instance properties/manifest files in the installation directory.
    Affected if Installed version falls within 11.7.0 to 11.7.17 (inclusive), 12.2.0 to 12.2.12 (inclusive), or any Innovation version below 12.8.0
  3. Verify if WEB transport is enabled
    Inspect the PASOE instance configuration files, specifically the 'openedge.properties' or 'ubroker.properties' file, and look for the WEB transport adapter configuration. Check if the WEB transport listener is active on its configured port.
    Affected if WEB transport is enabled and accessible on a network-exposed port
  4. Review PASOE logs for anomalous file upload attempts
    Examine the PASOE logs in the 'logs' directory of the instance for suspicious WEB transport requests, particularly those containing path traversal sequences or unusual file upload patterns.
    Affected if Log entries show unauthorized file upload requests with arbitrary path destinations
  5. Inspect server filesystem for unexpected uploaded files
    Check directories outside the expected PASOE webapps or temp directories for newly created files, particularly in system directories or configuration locations that should not be writable by the web application.
    Affected if Files exist in unexpected locations that correlate with WEB transport upload activity

A system is affected if Progress PAS for OpenEdge is installed with a version below 11.7.18, below 12.2.13, or below 12.8.0 for Innovation editions, and the WEB transport is enabled and accessible.

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.18 / 12.2.13 / 12.8.0 or later
Fixed in 11.7.1812.2.1312.8.0
Interim mitigation

Upgrade PAS for OpenEdge to version 11.7.18, 12.2.13, 12.8.0 or later. If immediate patching is not feasible, implement network segmentation to restrict access to PASOE instances and deploy WAF rules to detect and block anomalous file upload requests.

Recommended fix High confidence

OpenEdge 11.7.18, 12.2.13, or 12.8.0 (Innovation) depending on current branch

  1. 1. Identify the current OpenEdge PAS version by checking the $DLC/version file or using the 'pv' command
  2. 2. Create a complete backup of the current PASOE installation including configuration files in $DLC/servers/pasoe and any deployed applications
  3. 3. Download the appropriate fixed version from Progress Customer Portal: 11.7.18 for 11.7.x branches, 12.2.13 for 12.2.x branches, or 12.8.0 for Innovation releases
  4. 4. Stop all PASOE instances using 'oeping.sh stop' or 'oeping.bat stop'
  5. 5. Install the upgrade following Progress OpenEdge installation documentation, ensuring to preserve existing configuration
  6. 6. After installation, verify the version number matches the fixed release
  7. 7. Start PASOE instances and verify normal operation
  8. 8. Test that file upload restrictions are properly enforced via WEB transport
Caveat Minimal - minor configuration adjustments may be needed; review Progress OpenEdge 11.7.18 and 12.2.13 release notes for specific changes

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

Fix this in Openedge Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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