CVE-2023-43035: IBM Sterling Control Center 6.2.1, 6.3.1, and 6.4.0 allows web pages to be stored locally which can be read by

Routine

MEDIUM 4.0DOWNGRADE

CVE-2023-43035 is a medium-severity flaw (CVSS 4.0) affecting sterling control center. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

IBM Sterling Control Center 6.2.1, 6.3.1, and 6.4.0 allows web pages to be stored locally which can be read by another user on the system.

Why this priority

No elevated risk signals yet

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

Risk facts

CVSS score	4.0 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.2% (top 95%)
CISA exploited list	No
Weakness	CWE-525
Published	2025-04-10
Last modified	2026-06-17

Publisher (CNA): IBM Corporation · Vendor: ibm

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

Am I affected?

Timeline

2025-04-10 14:15 UTCPublished CVE record published
2026-06-17 06:25 UTCUpdated Record last modified

ibm sterling control center DOWNGRADE

Affected: 6.2.1 · 6.3.1 · 6.4.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 6.2.1

1. Check installed version

apt-cache policy sterling-control-center || rpm -q sterling-control-center || sterling-control-center --version

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

apt-cache madison sterling-control-center sudo apt install sterling-control-center=<VERSION_BEFORE_6.2.1> sudo apt-mark hold sterling-control-center

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

dnf --showduplicates list sterling-control-center sudo dnf downgrade sterling-control-center-<VERSION_BEFORE_6.2.1> sudo dnf versionlock add sterling-control-center

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-2023-43035?

sterling control center: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2023-43035 being exploited?

CVE-2023-43035 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-2023-43035 affect?

CVE-2023-43035 affects sterling control center. Severity is medium (CVSS 4.0). IBM Sterling Control Center 6.2.1, 6.3.1, and 6.4.0 allows web pages to be stored locally which can be read by another user on the system.

How urgent is CVE-2023-43035?

Priority 15/100. No elevated risk signals yet.

Related CVEs

CVE-2023-42007 MEDIUM 5.4 DOWNGRADE IBM Sterling Control Center 6.2.1, 6.3.1, and 6.4.0 is vulnerable to cross-site scripting
CVE-2023-35894 MEDIUM 5.4 DOWNGRADE IBM Control Center 6.2.1 through 6.3.1 is vulnerable to HTTP header injection, caused by improper validation o

References

← Back to latest CVEs