Skip to content

Commit 8f7e76f

Browse files
committed
spelling: initialization
Signed-off-by: Josh Soref <[email protected]>
1 parent 0a4c724 commit 8f7e76f

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

java/ql/src/experimental/Security/CWE/CWE-665/InsecureRmiJmxEnvironmentConfiguration.qhelp

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
<overview>
77
<p>For special use cases some applications may implement a custom service which handles JMX-RMI connections.</p>
88

9-
<p>When creating such a custom service, a developer should pass a certain environment configuration to the JMX-RMI server initalisation,
9+
<p>When creating such a custom service, a developer should pass a certain environment configuration to the JMX-RMI server initialization,
1010
as otherwise the JMX-RMI service is susceptible to an unsafe deserialization vulnerability.</p>
1111

1212
<p>This is because the JMX-RMI service allows attackers to supply arbitrary objects to the service authentication
@@ -41,11 +41,11 @@ For this reason an initialization with a <code>null</code> environment is also v
4141

4242
<p>The first example shows how an JMX server is initialized securely with the <code>JMXConnectorServerFactory.newJMXConnectorServer()</code> call.</p>
4343

44-
<sample src="CorrectJMXConnectorServerFactoryEnvironmentInitialisation.java" />
44+
<sample src="CorrectJMXConnectorServerFactoryEnvironmentInitialization.java" />
4545

4646
<p>The second example shows how a JMX Server is initialized securely if the <code>RMIConnectorServer</code> class is used.</p>
4747

48-
<sample src="CorrectRMIConnectorServerEnvironmentInitalisation.java" />
48+
<sample src="CorrectRMIConnectorServerEnvironmentInitialization.java" />
4949

5050
</example>
5151

0 commit comments

Comments
 (0)