Pensar - auto fix for Unbounded Tweet Retrieval Resource Exhaustion

[pensarappdev]

1. Unchecked Resource Consumption (CWE-400) in user_lookup_tweepy and user_lookup_sns:
   • A new class constant MAX_TWEETS = 3200 is introduced for the upper bound.
   • In both user_lookup_tweepy and user_lookup_sns, added:
     • Type check: If quantity is not an integer, a ValueError is raised.
     • Bounds check: If quantity is less than 1 or greater than MAX_TWEETS, a ValueError is raised.
   • For user_lookup_sns, corrected the stopping condition to if idx >= quantity: break to accurately return the requested number of tweets.
   • These checks prevent excessive resource usage and enforce consistency with Twitter API limits, fully mitigating the risk of denial-of-service via unbounded iteration or API overuse.

More Details

Type	Identifier	Message	Severity	Link
Application	CWE-400	The quantity parameter is taken directly from the caller without any validation or upper-bound check. A malicious or careless caller can request an extremely large number of tweets (e.g., millions), driving the loop to make a massive number of API calls and store all results in memory. This can (1) exhaust system resources (CPU, RAM, network), (2) exceed Twitter API rate limits—potentially causing the token to be throttled or banned, and (3) create a denial-of-service condition for any runtime that shares these resources. This is an instance of Uncontrolled Resource Consumption (CWE-400).	medium	Link