CVE-2024-7654
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 · uneditedAn ActiveMQ Discovery service was reachable by default from an OpenEdge Management installation when an OEE/OEM auto-discovery feature was activated. Unauthorized access to the discovery service's UDP port allowed content injection into parts of the OEM web interface making it possible for other types of attack that could spoof or deceive web interface users. Unauthorized use of the OEE/OEM discovery service was remediated by deactivating the discovery service by default.
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 confidenceThe ActiveMQ Discovery service UDP port was exposed by default in OpenEdge Management when the OEE/OEM auto-discovery feature was activated. This allowed unauthenticated remote attackers to inject arbitrary content into parts of the OEM web interface through the discovery mechanism, enabling spoofing and social engineering attacks against users.
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<= 11.7.19>= 12.2, <= 12.2.14>= 12.8, < 12.8.3CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Verify OpenEdge Management is installedIdentify if Progress OpenEdge Management (OEM) is running in your environment by checking for OEM processes or web interface accessAffected if OEM is installed and running
-
Check the installed OpenEdge versionLocate the OpenEdge installation and determine the exact version number installed in your environmentAffected if The version is 11.7.19 or earlier, 12.2.14 or earlier, or 12.8.0 through 12.8.2
-
Determine if OEE/OEM auto-discovery is enabledExamine the OEM configuration to verify whether the auto-discovery feature is currently activeAffected if The auto-discovery feature is enabled and running
-
Check for ActiveMQ Discovery UDP port exposureVerify if UDP port 1199 (or the configured discovery port) is accessible from your network interfaces and potentially from untrusted networksAffected if The ActiveMQ Discovery UDP port is exposed and accessible from untrusted networks
Your environment is affected if you are running a vulnerable OpenEdge version with the OEE/OEM auto-discovery feature enabled and the ActiveMQ Discovery UDP port is exposed to untrusted networks.
Generated from the published advisory. Verify against your own configuration.
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 · scoped12.8.3
Deactivate the OEE/OEM auto-discovery feature when not required, and ensure the ActiveMQ Discovery UDP port is not accessible from untrusted networks.
12.8.3 (for 12.8.x branches); 12.2.15+ (for 12.2.x branches); 11.7.20+ (for 11.7.x branches)
- In OpenEdge Management (OEM) or OpenEdge Explorer (OEE), navigate to the discovery service configuration
- Disable or deactivate the ActiveMQ discovery service that was auto-discovered
- Alternatively, ensure the UDP multicast port used by the discovery service is blocked or not accessible from untrusted networks
- After disabling the discovery service, verify that the OEM/OEE web interface no longer accepts injected content from the discovery channel
- Restart the OEM/OEE web server if required to apply configuration changes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7654 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-7654 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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