Skip to main content
assistive.skiplink.to.breadcrumbs
assistive.skiplink.to.header.menu
assistive.skiplink.to.action.menu
assistive.skiplink.to.quick.search

Rule 09. Locking (LCK)

Created by Dhruv Mohindra, last modified by Robert Seacord on Apr 29, 2015

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Rules

Page:

LCK00-J. Use private final lock objects to synchronize classes that may interact with untrusted code
Page:

LCK01-J. Do not synchronize on objects that may be reused
Page:

LCK02-J. Do not synchronize on the class object returned by getClass()
Page:

LCK03-J. Do not synchronize on the intrinsic locks of high-level concurrency objects
Page:

LCK04-J. Do not synchronize on a collection view if the backing collection is accessible
Page:

LCK05-J. Synchronize access to static fields that can be modified by untrusted code
Page:

LCK06-J. Do not use an instance lock to protect shared static data
Page:

LCK07-J. Avoid deadlock by requesting and releasing locks in the same order
Page:

LCK08-J. Ensure actively held locks are released on exceptional conditions
Page:

LCK09-J. Do not perform operations that can block while holding a lock
Page:

LCK10-J. Use a correct form of the double-checked locking idiom
Page:

LCK11-J. Avoid client-side locking when using classes that do not commit to their locking strategy

Risk Assessment Summary

Rule	Severity	Likelihood	Remediation Cost	Priority	Level
LCK00-J	low	probable	medium	P4	L3
LCK01-J	medium	probable	medium	P8	L2
LCK02-J	medium	probable	medium	P8	L2
LCK03-J	medium	probable	medium	P8	L2
LCK04-J	low	probable	medium	P4	L3
LCK05-J	low	probable	medium	P4	L3
LCK06-J	Medium	Probable	Medium	P8	L2
LCK07-J	Low	Likely	High	P3	L3
LCK08-J	low	likely	low	P9	L2
LCK09-J	low	probable	high	P2	L3
LCK10-J	low	probable	medium	P4	L3
LCK11-J	low	probable	medium	P4	L3

No labels