Skip to main content

AWS Lambda security risks

And here is the list of top Lambda security risks:

1. Function event data injection: Injection flaws in applications are one of the most common risks and can be triggered not only through untrusted input such as through a web API call but due to the potential attack surface of serverless architecture, can also come from cloud storage events, NoSQL databases, code changes, message queue events and IoT telemetry signals, among others.

2. Broken authentication: Applications built for serverless architectures often contain dozens -- or even hundreds -- of serverless functions, each with a specific purpose.

These functions connect together to form overall system logic, but some of these functions may expose public web APIs, others may consume events from different source types, and others may have coding issues ripe for exploit and attacks, which lead to unauthorized authentication.

3. Insecure serverless deployment configuration: The security firm found that incorrect settings and the misconfiguration of cloud services are a common theme. This, in turn, can provide an entry point for attacks against serverless architectures, the leak of sensitive, confidential information, and potentially Man-in-The-Middle (MiTM) attacks.

4. Over-privileged function permissions and roles: Serverless applications -- and enterprise systems as a whole -- should follow the principle of "least privilege."

5. Inadequate function monitoring and logging: The reconnaissance phase of an attack, where threat actors attempt to gain intel on a network's defenses and weaknesses, is also a crucial point for cybersecurity solutions to detect suspicious behavior and shut it down.

6. Insecure third-party dependencies: When serverless functions rely on third-party software, such as open-source packages and libraries, if vulnerabilities are present, these can pave the way for exploit.

7. Insecure application secrets storage: Many apps require "secret" information to be encrypted and stored, such as API keys, passwords, configuration settings, and database credentials.

8. DDoS attacks, resources stretched to the limit: According to the study, distributed denial-of-service (DDoS) attacks pose a serious risk to serverless architecture as there may be memory allocation, duration per function, and execution limits.

9. Serverless function execution flow manipulation: Attackers may be able to subvert application logic by tampering with application flows, leading to access control bypass, privilege escalation or denial-of-service attacks.

10. Improper exception handling and verbose error messages: Line-by-line debugging services for serverless architecture are often rather limited. As a result, some developers adopt verbose error messages, enable debugging after the fact, and they may forget to clean the code when it is moved to production.
Reference: OWASP/ PurSec


Popular posts from this blog

Ardilla- New tool for finding SQL Injection and XSS

Three Researchers -- MIT's Adam Kiezun , Stanford's Philip Guo , and Syracuse University's Karthick Jayaraman -- has developed a new tool ' Ardilla ' that automatically finds and exploits SQL injection and cross-site scripting vulnerabilities in Web applications. It creates inputs that pinpoint bugs in Web applications and then generates SQL injection and XSS attacks. But for now Ardilla is for PHP -based Web app only. The researchers say Ardilla found 68 never-before found vulnerabilities in five different PHP applications using the tool -- 23 SQL injection and 45 XSS flaws. More information is awaited. For their attack generation techniques refer to their document at:

Combining power of Fiddler with Burp

Both are pretty powerful tools when it comes to intercept and modify http communications. But at some point of time, they become even more powerful combo if tied with each other. They complement each other. In a recent pentest I came across a similar situation where in Burp was not able to intercept a specific kind of traffic and Fiddler came to rescue. The application was designed to upload video. The initial communication was straight forward, I mean logging into application, filling up the video details etc. And all these were easily captured by Burp except the point where you hit the Upload Video and it connects to a different server and surprisingly it was not captured by Burp, not sure why, even after repeated attempts. So, I fired Fiddler to see if the it sees this request. But it's a;ways to play with requests using Burp due to it's various functionalities like, Intruder, Repeaters etc. But it was necessary to capture this request in Burp. So the below steps can be

File Upload through Null Byte Injection

Sometimes, during file upload we come across situation wherein there would be check on the file extension at the client side as well as server side too. If the application does allow only .jpeg extension to be uploaded, the client side java script checks for the extension of the file before passing the request. We all know that how easily this can be defeated. Some applications, checks for the extension at the server side also. That's not easy to bypass. However there are some ways with which it still can be bypassed. Most of server side scripts are written in high level languages such as Php, Java etc who still use some C/C++ libraries to read the file name and contents. That leads to the problem. In C/C++ a line ends with /00 or which is called Null Byte. So whenever the interpreter sees a null byte at the end of the a string, it stops reading thinking it has reached at the end of the string. This can be used for the bypass. It works for many servers, specially php servers. T