dbcve.org
OpenedgeWeb browser · Progress

CVE-2023-40052

HIGH · 7.5 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 →
84/100
Remediation priority · High
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
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 who can produce a malformed web request may cause the crash of a PASOE agent potentially disrupting the thread activities of many web application clients. Multiple of these DoS attacks could lead to the flooding of invalid requests as compared to the server’s remaining ability to process valid requests.

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 malformed web request can crash PASOE (Progress Application Server for OpenEdge) agents, disrupting thread activities for multiple web application clients simultaneously. Repeated exploitation can lead to sustained denial of service as the server becomes overwhelmed with invalid requests.

MitigationApply the vendor patches: upgrade to PAS for OpenEdge 11.7.18, 12.2.13, 12.8.0 or later to resolve this 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, < 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Confirm PASOE is installed
    Locate the OpenEdge installation directory and verify the presence of PASOE (Progress Application Server for OpenEdge) components. Common locations include $DLC (OpenEdge installation root) or C:\Progress\OpenEdge on Windows. Look for the 'pasoe' subdirectory or related binaries.
    Affected if PASOE components are not found - the system is not using this product
  2. Identify the OpenEdge version
    Run the command 'proversion' from the OpenEdge bin directory, or check the version file in the installation root. On Windows, this may also be visible in the Windows Services panel if PASOE runs as a service.
    Affected if Unable to determine version - cannot assess vulnerability status
  3. Compare version against affected ranges
    Check if the installed version falls within: 11.7.0 to 11.7.17 (inclusive), 12.2.0 to 12.2.12 (inclusive), or any Innovation release below 12.8.0. Any of these ranges indicate the environment is vulnerable.
    Affected if Version is 11.7.x where x < 18, OR 12.2.x where x < 13, OR 12.x Innovation where x < 8.0
  4. Verify PASOE web listener is exposed
    Check if PASOE is configured to accept web requests. Review the PASOE configuration files (openedge.properties or pasman.xml) in the instance directory for enabled web adapters or listeners. Confirm the PASOE agent processes are running.
    Affected if PASOE is not configured or not running - the attack surface may not be exposed but the vulnerable code is still present if version is affected

A user is affected if OpenEdge PASOE is installed with a version in 11.7.0-11.7.17, 12.2.0-12.2.12, or any Innovation release below 12.8.0, regardless of whether the service is currently running.

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

Apply the vendor patches: upgrade to PAS for OpenEdge 11.7.18, 12.2.13, 12.8.0 or later to resolve this vulnerability.

Recommended fix High confidence

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

  1. Identify the current installed version of OpenEdge PAS (e.g., 11.7.x, 12.2.x, or Innovation release)
  2. Download the corresponding fixed version from the Progress Customer Portal: 11.7.18 for 11.7.x releases, 12.2.13 for 12.2.x releases, or 12.8.0 for Innovation releases
  3. Review the Progress OpenEdge upgrade documentation for your specific version
  4. Perform the upgrade following standard Progress upgrade procedures
  5. After upgrade, validate that PASOE agents remain stable and do not crash on malformed web requests
  6. Monitor server logs to confirm the vulnerability is remediated
Caveat Standard upgrade considerations apply - test in non-production environment first; no specific breaking changes mentioned in advisory

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

Fix this in Openedge Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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