> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/security/security-bulletins/cve-2022-22965-security-vulnerability-spring4shell-spring-framework.md).

# CVE-2022-22965 - Security Vulnerability Spring4shell - Spring Framework

## Vulnerability statement <a href="#cve-2022-22965-securityvulnerabilityspring4shell-springframework-vulnerabilitystatement" id="cve-2022-22965-securityvulnerabilityspring4shell-springframework-vulnerabilitystatement"></a>

Upon receiving reports of the Spring4Shell software vulnerability, the Nexthink Security team analyzed to determine any potential impacts on our systems.

## Vulnerability summary <a href="#cve-2022-22965-securityvulnerabilityspring4shell-springframework-vulnerabilitysummary" id="cve-2022-22965-securityvulnerabilityspring4shell-springframework-vulnerabilitysummary"></a>

* The Spring Framework is an application framework and inversion of the control container for the Java platform.
* On March 31, 2022, a critical vulnerability (CVE-2022-22965) impacting the Spring Framework was reported, resulting in patches from the vendor.
* This vulnerability is being widely exploited in the wild.

## Are Collector and the client-side components affected? <a href="#cve-2022-22965-securityvulnerabilityspring4shell-springframework-arecollectorandtheclient-sidecompon" id="cve-2022-22965-securityvulnerabilityspring4shell-springframework-arecollectorandtheclient-sidecompon"></a>

Collector and the client-side components (Finder, Data Enricher, Event Connector and Chatbot SDK) do not use the affected library.

## Is the Nexthink Experience platform affected? <a href="#cve-2022-22965-securityvulnerabilityspring4shell-springframework-isthenexthinkexperienceplatformaffe" id="cve-2022-22965-securityvulnerabilityspring4shell-springframework-isthenexthinkexperienceplatformaffe"></a>

The cloud-based components do not use the library in the affected configuration.

## Are the Nexthink corporate network and supply chain affected? <a href="#cve-2022-22965-securityvulnerabilityspring4shell-springframework-arethenexthinkcorporatenetworkandsu" id="cve-2022-22965-securityvulnerabilityspring4shell-springframework-arethenexthinkcorporatenetworkandsu"></a>

Our Security team also performed a vulnerability assessment with our third-party vendors to ensure that this vulnerability does not impact the services they provide us with.

## How is Nexthink protecting its product against vulnerabilities? <a href="#cve-2022-22965-securityvulnerabilityspring4shell-springframework-howisnexthinkprotectingitsproductag" id="cve-2022-22965-securityvulnerabilityspring4shell-springframework-howisnexthinkprotectingitsproductag"></a>

Our Engineering Security policy and Vulnerability Management policy (which can be shared under NDA) describe high-level principles we apply to detect, mitigate and patch these vulnerabilities. The secure software development lifecycle is an integral part of our security program. Nexthink implemented several security controls to detect vulnerabilities from the early design stages to the release of the product and cloud offering. It includes, but is not limited to, design reviews, penetration tests of different components, vulnerability scans, third-party library assessments and code reviews.

## References <a href="#cve-2022-22965-securityvulnerabilityspring4shell-springframework-references" id="cve-2022-22965-securityvulnerabilityspring4shell-springframework-references"></a>

<https://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nexthink.com/security/security-bulletins/cve-2022-22965-security-vulnerability-spring4shell-spring-framework.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.