Tag: security-context
Unspecified defaults can cause your application to crash.
Missing check on the value returned by moveToFirst API can cause your application to crash.
Deserializing objects from relational databases should allocate a 64-bit, not 32-bit, type for the auto-incremented identifier.
Calls to mutually exclusive methods were found in the code.
Reuse AWS clients in Lambda.
Missing check on the result of createNewFile might cause data loss.
Synchronized objects should not be re-assigned in the same synchronized
block because the references to the synchronized object would be lost.
Recreating AWS clients in each Lambda function invocation is expensive.
If a method that uses an input parameter to update an output value throws an exception, then the output value is not updated.
Improper use of locks in a multi-threaded program can lead to deadlock and cause the program to be unresponsive.
Overriding environment variables that are reserved by AWS Lambda might lead to unexpected behavior.
APIs that are not recommended were found.
Always call super.finalize
explicitly.
Failure to specify a content length causes the contents of the input stream to buffer locally in memory in order to calculate its length. This can result in performance problems.
An outdated or bad parameters were detected in calls to some AWS API methods.
Uploading objects to Amazon S3 by using streams (either through an AmazonS3 client or TransferManager
) might encounter network connectivity or timeout issues.
Not setting the S3 bucket owner condition might introduce a risk of accidentally using a wrong bucket.
Public method parameters should be validated for nullness, unexpected values, and malicious values.
Missing check on the value returned by ResultSet.next can cause your application to crash.
User metadata keys are case insensitive and are returned as lowercase strings, even if they were originally specified with uppercase strings.
When re-throwing an exception, make sure to include the stack trace.
Check if errors are returned by DynamoDBMapper
's BatchWrite
operations.
Dereferencing a null pointer can lead to unexpected null pointer exceptions.
Atomicity violations caused by improper usage of ConcurrentHashMap
or ConcurrentLinkedQueue
can result in crashses or incorrect program results.
Catching generic exceptions might hide issues when specific exceptions are thrown.
It's not good practice to catch an exception and then re-throw or log it.
Your application can crash if the check for an application that can receive the implicit intent is missing from code.
Use numeric types that are large enough to hold the result of arithmetic operations.
Additional results are not checked for a paginated API call. This might produce inaccurate results.
Call ShutdownNow
when you use TransferManager
to manage transfers to Amazon S3.
Using a SimpleDateFormat
object without setting its timezone can result in unexpected date and time.
Insufficiently random generators (or hardcoded seeds) can make pseudorandom sequences predictable.
Unhandled failures of deleting files can exhaust file handles.