CVE-2002-2127: Integrity Protection Driver (IPD) 1.2 and earlier blocks access to \Device\PhysicalMemory by its name, which c

Routine

LOW 2.1DOWNGRADE

CVE-2002-2127 is a low-severity flaw (CVSS 2.1) affecting integrity protection driver. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Integrity Protection Driver (IPD) 1.2 and earlier blocks access to \Device\PhysicalMemory by its name, which could allow local privileged processes to overwrite kernel memory by accessing the device through a symlink.

Why this priority

No elevated risk signals yet

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

Risk facts

CVSS score	2.1 (Low)
EPSS exploit chance	0.3% (top 72%)
CISA exploited list	No
Published	2002-12-31
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: pedestal software

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

Am I affected?

Timeline

2002-12-31 05:00 UTCPublished CVE record published
2026-06-16 22:00 UTCUpdated Record last modified

pedestal software integrity protection driver DOWNGRADE

Affected: 1.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.2

1. Check installed version

apt-cache policy integrity-protection-driver || rpm -q integrity-protection-driver || integrity-protection-driver --version

2. No fixed release: DOWNGRADE to a release before 1.2 (Debian / Ubuntu)

apt-cache madison integrity-protection-driver sudo apt install integrity-protection-driver=<VERSION_BEFORE_1.2> sudo apt-mark hold integrity-protection-driver

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list integrity-protection-driver sudo dnf downgrade integrity-protection-driver-<VERSION_BEFORE_1.2> sudo dnf versionlock add integrity-protection-driver

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-2002-2127?

integrity protection driver: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2002-2127 being exploited?

CVE-2002-2127 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-2002-2127 affect?

CVE-2002-2127 affects integrity protection driver. Severity is low (CVSS 2.1). Integrity Protection Driver (IPD) 1.2 and earlier blocks access to \Device\PhysicalMemory by its name, which could allow local privileged processes to overwrite kernel memory by accessing the device through a symlink.

How urgent is CVE-2002-2127?

Priority 14/100. No elevated risk signals yet.

Related CVEs

CVE-2004-1718 LOW 2.1 DOWNGRADE The ZwOpenSection function in Integrity Protection Driver (IPD) 1.4 and earlier allows local users to cause a
CVE-2003-1246 LOW 2.1 DOWNGRADE NtCreateSymbolicLinkObject in ntdll.dll in Integrity Protection Driver (IPD) 1.2 and 1.3 allows local users to
CVE-2003-1233 CRITICAL 9.8 UPGRADE Pedestal Software Integrity Protection Driver (IPD) 1.3 and earlier allows privileged attackers, such as rootk
CVE-2002-2126 LOW 2.1 DOWNGRADE restrictEnabled in Integrity Protection Driver (IPD) 1.2 delays driver installation for 20 minutes, which allo

References

← Back to latest CVEs