== Why is this an issue?

Dynamically loaded classes could contain malicious code executed by a static class initializer. I.E. you wouldn't even have to instantiate or explicitly invoke methods on such classes to be vulnerable to an attack.


This rule raises an issue for each use of dynamic class loading.

=== Noncompliant code example

[source,java]
----
String className = System.getProperty("messageClassName");
Class clazz = Class.forName(className);  // Noncompliant
----

include::../see.adoc[]

ifdef::env-github,rspecator-view[]

'''
== Implementation Specification
(visible only on this page)

=== Message

Remove this use of dynamic class loading.


'''
== Comments And Links
(visible only on this page)

include::../comments-and-links.adoc[]

endif::env-github,rspecator-view[]