CVE-2007-3491
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 · uneditedBuffer overflow in _mprosrv in Progress Software OpenEdge before 9.1E0422, and 10.x before 10.1B01, allows remote attackers to have an unknown impact via a malformed TCP/IP message.
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 · moderate confidenceBuffer overflow vulnerability in the _mprosrv component of Progress Software OpenEdge allows remote attackers to execute arbitrary code or cause denial of service via malformed TCP/IP messages sent to the server. The vulnerability exists in versions prior to 9.1E0422 and 10.1B01.
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= 9.1e= 10.1a= 10.1bCVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 Progress OpenEdge installationLook for OpenEdge installation directories (common paths: C:\Progress\OpenEdge on Windows, /usr/dlc/ on UNIX/Linux). Check for the presence of OpenEdge executables and the _mprosrv component.Affected if OpenEdge is not installed on the system - no further action needed.
-
Identify installed OpenEdge versionRun 'pro version' command from the OpenEdge bin directory, or check version information in the installation's about dialog or version file. The version string typically appears as 9.1E, 10.1A, 10.1B, or similar.Affected if Unable to determine version - assume potentially affected if OpenEdge is present.
-
Confirm _mprosrv component is enabledCheck if the _mprosrv process is running or configured to start. On Windows, view services or check for _mprosrv.exe in task list. On UNIX/Linux, run 'ps -ef | grep mprosrv'. Review OpenEdge configuration files for _mprosrv service settings.Affected if _mprosrv is not running or not configured - the specific vulnerability is not currently exploitable, but the unpatched version still poses risk if enabled later.
-
Compare version against affected rangesThe affected (vulnerable) versions are: 9.1E (all builds prior to 9.1E0422), 10.1A (all builds), and 10.1B builds prior to 10.1B01. If your installed version falls into any of these ranges and _mprosrv is enabled, the system is affected by this CVE.Affected if Installed version is 9.1E before build 0422, 10.1A at any build, or 10.1B before build 01, AND _mprosrv is accessible on the network.
System is affected if Progress OpenEdge is installed with version 9.1E (pre-9.1E0422), 10.1A, or 10.1B (pre-10.1B01), and the _mprosrv TCP/IP service is enabled and network-accessible.
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.
From vendor dataUpgrade OpenEdge to version 9.1E0422 or later, or 10.1B01 or later. If immediate patching is not feasible, consider network segmentation to restrict unauthorized access to the _mprosrv service.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-3491 — 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-2007-3491 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