...
Compliance with LCK00-J. Use private final lock objects to synchronize classes that may interact with untrusted code can reduce the likelihood of misuse by ensuring that untrusted callers cannot access the lock object.
Exceptions
VNA00-J-EX0: Class objects are created by the virtual machine; their initialization always precedes any subsequent use. Consequently, cross-thread visibility of Class objects is already assured by default.
...
Failing to ensure the visibility of a shared primitive variable may result in a thread observing a stale value of the variable.
Rule | Severity | Likelihood | Remediation Cost | Priority | Level |
|---|---|---|---|---|---|
VNA00-J | Medium | Probable | Medium | P8 | L2 |
Automated Detection
Some static analysis tools are capable of detecting violations of this rule.
| Tool | Version | Checker | Description | ||||||
|---|---|---|---|---|---|---|---|---|---|
| CodeSonar |
| JAVA.CONCURRENCY.LOCK.ICS | Impossible Client Side Locking (Java) | ||||||
| Eclipse | 4.2.0 |
| Not Implemented | ||
| FindBugs | 2.0.1 |
| Not Implemented | |||||||||
| Parasoft Jtest |
| CERT.VNA00.LORD CERT.VNA00.MRAV | Ensure that nested locks are ordered correctly Access related Atomic variables in a synchronized block | ||||||
| PMD | 5.0.0 |
| Not Implemented | ||
| Fortify |
| Not Implemented | |||||||||
| Coverity | 7.5 | SERVLET_ATOMICITY | Implemented | ||||||
| ThreadSafe |
| CCE_SL_INCONSISTENT | Implemented |
Related Guidelines
CWE-413, Improper |
Resource Locking |
Access to |
Shared Data in a |
Multithreaded Context |
Bibliography
Item 66, "Synchronize Access to Shared Mutable Data" | |
Section 3.4.2, "Example: Using Volatile to Publish Immutable Objects" | |
[JLS 2015] | Chapter 17, "Threads and Locks" |
[JPL 2006] | Section 14.10.3, "The Happens-Before Relationship" |
...
...