Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2003-0030: Buffer overflows in protegrity.dll of Protegrity Secure.Data Extension Feature (SEF) before 2.2.3.9 allow atta

58
This month
HIGH 10.0DOWNGRADE

CVE-2003-0030 is a high-severity flaw (CVSS 10.0) affecting secure.data. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Buffer overflows in protegrity.dll of Protegrity Secure.Data Extension Feature (SEF) before 2.2.3.9 allow attackers with SQL access to execute arbitrary code via the extended stored procedures (1) xp_pty_checkusers, (2) xp_pty_insert, or (3) xp_pty_select.

Why this priority

  • Critical severity
  • EPSS top 8%: very likely to be exploited

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score10.0 (High)
EPSS exploit chance4.8% (top 8%)
CISA exploited listNo
Published2003-03-18
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: protegrity

Share: LinkedIn · X · Reddit

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

protegrity secure.data DOWNGRADE
Affected: 2.2.3.7 · 2.2.3.8
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.2.3.7
1. Check installed version
apt-cache policy secure.data || rpm -q secure.data || secure.data --version
2. No fixed release: DOWNGRADE to a release before 2.2.3.7 (Debian / Ubuntu)
apt-cache madison secure.data sudo apt install secure.data=<VERSION_BEFORE_2.2.3.7> sudo apt-mark hold secure.data
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list secure.data sudo dnf downgrade secure.data-<VERSION_BEFORE_2.2.3.7> sudo dnf versionlock add secure.data
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2003-0030?

secure.data: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2003-0030 being exploited?

CVE-2003-0030 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2003-0030 affect?

CVE-2003-0030 affects secure.data. Severity is high (CVSS 10.0). Buffer overflows in protegrity.dll of Protegrity Secure.Data Extension Feature (SEF) before 2.2.3.9 allow attackers with SQL access to execute arbitrary code via the extended stored procedures (1) xp_pty_checkusers, (2) xp_pty_insert, or (3

How urgent is CVE-2003-0030?

Priority 58/100. Critical severity; EPSS top 8%: very likely to be exploited

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.