class TrustBoundaryViolationValueDetector extends BasicInjectionDetector {

    public TrustBoundaryViolationValueDetector(BugReporter bugReporter) {
        super(bugReporter);
        loadConfiguredSinks("trust-boundary-violation-value.txt", "TRUST_BOUNDARY_VIOLATION");
    }

    /**=
     * All or nothing :
     * <ul>
     * <li>If the taint to sink path is found, it is mark as high</li>
     * <li>If the source is not confirm, it is mark as low. This is will be the most common case.</li>
     * </ul>
     * @param taint Taint state
     * @return High or low confidence
     */
    @Override
    protected int getPriority(Taint taint) {<FILL_FUNCTION_BODY>}
}

        //**Low risk**
        //It is very common that variable are not sanetize and store in session.
        //By it self it pose little risk. The thinking is the injection or the critical operation
        //will be catch.
        //After all storing value in the session is not so different to storing value in local variables or any indirection.
        //**False positive**
        //The usual and most common configuration is to hide LOW priority (confidence).
        //This way this FP producer will not polute day to day review by developers.

        if (taint.isTainted() || !taint.isSafe()) {
            return Priorities.LOW_PRIORITY;
        }
        else {
            return Priorities.IGNORE_PRIORITY;
        }
    
<methods>public void registerVisitor(com.h3xstream.findsecbugs.taintanalysis.TaintFrameAdditionalVisitor) <variables>static com.h3xstream.findsecbugs.injection.ClassMethodSignature OBJECT,private static final com.h3xstream.findsecbugs.injection.SinksLoader SINKS_LOADER,private final Map<com.h3xstream.findsecbugs.injection.ClassMethodSignature,com.h3xstream.findsecbugs.injection.InjectionPoint> injectionMap