public class TrustBoundaryViolationAttributeDetector extends BasicInjectionDetector
Trust Boundary Violation is fancy name to describe tainted value passed directly to session attribute. This could be an expected behavior that allow an attacker to change the session state.
When the attribute name is dynamic, it is a lot more suspicious than when it is a dynamic value.
setAttribute( suspiciousValue, "true")
vs
setAttribute( "language" , commonDynamicValue)
For this reason, the trust boundary violation was split in two detector.
TrustBoundaryViolationValueDetectorinjectionSinksbugReporter| Constructor and Description |
|---|
TrustBoundaryViolationAttributeDetector(edu.umd.cs.findbugs.BugReporter bugReporter) |
| Modifier and Type | Method and Description |
|---|---|
protected int |
getPriority(Taint taint)
All or nothing :
If the taint to sink path is found, it is mark as high
If the source is not confirm, it is mark as low.
|
addParsedInjectionPoint, getInjectionPoint, loadConfiguredSinks, loadConfiguredSinks, loadCustomConfigFiles, loadCustomSinks, loadSinkanalyzeLocation, getPriorityFromTaintFrame, reportanalyzeMethod, shouldAnalyzeClass, visitClassContextpublic TrustBoundaryViolationAttributeDetector(edu.umd.cs.findbugs.BugReporter bugReporter)
protected int getPriority(Taint taint)
getPriority in class AbstractInjectionDetectortaint - Taint stateCopyright © 2017. All rights reserved.