VMware vCenter Server: improper access control flaw under attack

What is affected

VMware vCenter Server is mostly run by companies, schools and public bodies, not on home computers. You are unlikely to have it yourself, but organisations that hold your data may. Breaches that start with flaws like this one are how personal data ends up leaked.

Rhttproxy as used in vCenter Server contains a vulnerability due to improper implementation of URI normalization.

What an attacker can do

This is a improper access control flaw. It lets an attacker perform actions or reach data that should be restricted to authorised users.

How it is reached

Over the internet or network

Access the attacker needs

No account needed

Does the victim have to do something?

No, works without the victim doing anything

What to do

1. At home: nothing to install. Keep your own devices updated and use a different password for every service, so that a breach at one organisation does not open your other accounts.
2. If you administer VMware vCenter Server at work: apply the vendor's fix or mitigation now and review logs for signs of compromise, because the flaw was being exploited before it was listed.
3. If the product is past its support date and no fix exists, take it off the internet or retire it.

Apply updates per vendor instructions.

How urgent is it

CISA added this vulnerability to its Known Exploited Vulnerabilities catalogue on January 10, 2022, which means there is reliable evidence of attacks in the wild. US federal agencies must fix it by January 24, 2022, a deadline that has already passed. That deadline does not bind anyone else, but it shows how seriously the agency rates it.

The EPSS model estimates a 49% probability that this flaw will be exploited somewhere in the next 30 days. That is higher than 99% of all scored vulnerabilities.

Its CVSS severity score is 5.3 out of 10 (medium), as recorded in the US National Vulnerability Database.

Technical description

Rhttproxy as used in vCenter Server contains a vulnerability due to improper implementation of URI normalization. A malicious actor with network access to port 443 on vCenter Server may exploit this issue to bypass proxy leading to internal endpoints being accessed.