What is CVE-2022-32155?A high-severity flaw in Splunk, explained.
CVE-2022-32155 is a high-severity flaw (CVSS 7.5) in Splunk, published on 15 June 2022. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 2.0%. If you run an affected version, plan in the vendor’s fix.
Published 15 June 2022. Record last updated 24 June 2022. We keep this page's data up to date.
What is CVE-2022-32155? In plain terms.
It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data.
In universal forwarder versions before 9.0, management services are available remotely by default. When not required, it introduces a potential exposure, but it is not a vulnerability. If exposed, we recommend each customer assess the potential severity specific to your environment. In 9.0, the universal forwarder now binds the management port to localhost preventing remote logins by default. If management services are not required in versions before 9.0, set disableDefaultPort = true in server.conf OR allowRemoteLogin = never in server.conf OR mgmtHostPort = localhost in web.conf. See Configure universal forwarder management security (https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation#Configure_universal_forwarder_management_security) for more information on disabling the remote management services.
What kind of flaw is it?
- CWE-732Incorrect Permission Assignment for Critical Resource
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan read data
Severity vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Is CVE-2022-32155 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 2.0%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2022-32155 scores 46. Action: Plan remediation.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2022-32155 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2022-32155? 2 products.
The published record lists 2 products from 1 vendor. Versions are shown as published: "before 9.0" means every version up to, but not including, 9.0. If you run one of these, check your version, then go to the fix below.
- Application
Splunk
by Splunk
Affected versionsbefore 9.0 - Application
Splunk Cloud Platform
by Splunk
Affected versionsbefore 8.2.2106
How do I fix CVE-2022-32155? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
Does CVE-2022-32155 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
In universal forwarder versions before 9.0, management services are available remotely by default. When not required, it introduces a potential exposure, but...
- Matched to
- Splunk on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2022-32155 is a high-severity flaw in Splunk, published on 15 June 2022. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data.
It scores 7.5 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2022-32155 is 46 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 2.0%. That can change at any time, which is why we keep watching.
For Splunk: before 9.0. The record lists 2 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.