How severe is CVE-2001-1127?

CVE-2001-1127 has a CVSS 2.0 base score of 7.2, rated high severity.

Is CVE-2001-1127 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (82nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2001-1127?

CVE-2001-1127 primarily affects Progress. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2001-1127?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2001-1127 published?

CVE-2001-1127 was published on 2001-10-05 and last updated on 2026-06-16.

CVE-2001-1127

CVE-2001-1127 is a high-severity vulnerability in Progress with a CVSS 2.0 base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 2.0 base score 7.2)
EPSS exploit prediction: 2% (82nd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Progress
Published: 2001-10-05
Last modified: 2026-06-16

Description

Buffer overflow in Progress database 8.3D and 9.1C could allow a local user to execute arbitrary code via (1) _proapsv, (2) _mprosrv, (3) _mprshut, (4) orarx, (5) sqlcpp, (6) _probrkr, (7) _sqlschema and (8) _sqldump.

Frequently asked questions

What is CVE-2001-1127?: Buffer overflow in Progress database 8.3D and 9.1C could allow a local user to execute arbitrary code via (1) _proapsv, (2) _mprosrv, (3) _mprshut, (4) orarx, (5) sqlcpp, (6) _probrkr, (7) _sqlschema and (8) _sqldump.
How severe is CVE-2001-1127?: CVE-2001-1127 has a CVSS 2.0 base score of 7.2, rated high severity.
Is CVE-2001-1127 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (82nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2001-1127?: CVE-2001-1127 primarily affects Progress. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2001-1127?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2001-1127 published?: CVE-2001-1127 was published on 2001-10-05 and last updated on 2026-06-16.

References

Affected products (2)

cpe:2.3:a:progress:progress:8.3d:*:*:*:*:*:*:*
cpe:2.3:a:progress:progress:9.1c:*:*:*:*:*:*:*

More vulnerabilities in Progress

CVE-2007-2417 — Critical (CVSS 10.0): Heap-based buffer overflow in _mprosrv.exe in Progress Software Progress 9.1E and OpenEdge 10.1x, as used by the RSA…
CVE-2007-2506 — High (CVSS 7.8): WebSpeed 3.x in OpenEdge 10.x in Progress Software Progress 9.1e, and certain other 9.x versions, allows remote…
CVE-2001-1129 — High (CVSS 7.2): Format string vulnerabilities in (1) _probuild, (2) _dbutil, (3) _mprosrv, (4) _mprshut, (5) _proapsv, (6) _progres,…
CVE-2001-1128 — High (CVSS 7.2): Buffer overflow in Progress database 8.3D and 9.1C allows local users to execute arbitrary code via long entries in…

All CVEs affecting Progress →