dbcve.org
OpenedgeWeb browser · Progress

CVE-2024-7345

CRITICAL · 9.6 CVSS v3.1 Published 2024-09-03
Fix available
A fix is available. Upgrade to after 12.2.13 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Local ABL Client bypass of the required PASOE security checks may allow an attacker to commit unauthorized code injection into Multi-Session Agents on supported OpenEdge LTS platforms up to OpenEdge LTS 11.7.18 and LTS 12.2.13 on all supported release platforms

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

The local ABL Client in OpenEdge LTS can bypass required PASOE (Progress Application Server for OpenEdge) security checks, enabling unauthorized code injection into Multi-Session Agents. This security bypass allows an attacker to inject and execute arbitrary code within the MSA context, potentially compromising the entire application server.

MitigationApply the vendor-provided security patch for OpenEdge LTS versions 11.7.18 and earlier, and 12.2.13 and earlier. After patching, verify that Multi-Session Agents correctly enforce security checks and that no unauthorized code can be injected.

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.18>= 12.0, <= 12.2.13

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

CVSS:3.1/AV:A/AC:L/PR:N/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 installed OpenEdge LTS version
    Run 'proversion' command or check the OpenEdge installation directory for version information
    Affected if The version is 11.7.18 or earlier, or 12.0 through 12.2.13
  2. Verify PASOE is deployed
    Check for PASOE (Progress Application Server for OpenEdge) installation by looking for PASOE-related directories in the OpenEdge installation or checking for PASOE processes running
    Affected if PASOE is installed and running
  3. Confirm Multi-Session Agent configuration
    Check the PASOE configuration for Multi-Session Agent (MSA) settings, typically found in the PASOE instance configuration files such as openedge.properties or in the admin server manager
    Affected if Multi-Session Agents are enabled in the PASOE configuration
  4. Check for local ABL Client usage
    Review application deployment to determine if the local ABL Client (as opposed to remote ABL Client) is being used to connect to PASOE. This may be evident in connection strings or client configuration files
    Affected if The local ABL Client is being used to connect to PASOE with MSA enabled

A user is affected if they are running a vulnerable OpenEdge LTS version (11.7.18 or earlier, or 12.0-12.2.13) with PASOE deployed and Multi-Session Agents enabled, and the local ABL Client is used to connect to the application server.

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 a release after 12.2.13
Interim mitigation

Apply the vendor-provided security patch for OpenEdge LTS versions 11.7.18 and earlier, and 12.2.13 and earlier. After patching, verify that Multi-Session Agents correctly enforce security checks and that no unauthorized code can be injected.

Recommended fix Moderate confidence

OpenEdge LTS 11.7.19 or later; OpenEdge LTS 12.3.0 or later

  1. Identify the current OpenEdge LTS version in use by checking the installation or consulting inventory documentation
  2. Determine whether the deployment uses PASOE (Progress Application Server for OpenEdge) with Multi-Session Agents enabled
  3. For OpenEdge 11.x deployments: Plan upgrade to OpenEdge LTS 11.7.19 or later
  4. For OpenEdge 12.x deployments: Plan upgrade to OpenEdge LTS 12.3.0 or later
  5. Schedule maintenance window and coordinate with application teams
  6. Backup all configuration files, ABL applications, and database configurations before upgrade
  7. Execute upgrade following Progress documentation for your specific platform
  8. After upgrade, verify that PASOE security checks are properly enforced
Caveat Review LTS release notes for your specific version jump as there may be deprecated features or configuration changes; test thoroughly in non-production first

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

Fix this in Openedge Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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