Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-0560PUBLISHED: 2023-01-28
A vulnerability, which was classified as critical, has been found in SourceCodester Online Tours & Travels Management System 1.0. This issue affects some unknown processing of the file admin/practice_pdf.php. The manipulation of the argument id leads to sql injection. The attack may be initiated...
CVE-2023-0561PUBLISHED: 2023-01-28
A vulnerability, which was classified as critical, was found in SourceCodester Online Tours & Travels Management System 1.0. Affected is an unknown function of the file /user/s.php. The manipulation of the argument id leads to sql injection. It is possible to launch the attack remotely. The expl...
CVE-2023-23628PUBLISHED: 2023-01-28
Metabase is an open source data analytics platform. Affected versions are subject to Exposure of Sensitive Information to an Unauthorized Actor. Sandboxed users shouldn't be able to view data about other Metabase users anywhere in the Metabase application. However, when a sandbox user views the sett...
CVE-2023-23629PUBLISHED: 2023-01-28
Metabase is an open source data analytics platform. Affected versions are subject to Improper Privilege Management. As intended, recipients of dashboards subscriptions can view the data as seen by the creator of that subscription. This allows someone with greater access to data to create a dashboard...
CVE-2023-23616PUBLISHED: 2023-01-28
Discourse is an open-source discussion platform. Prior to version 3.0.1 on the `stable` branch and 3.1.0.beta2 on the `beta` and `tests-passed` branches, when submitting a membership request, there is no character limit for the reason provided with the request. This could potentially allow a user to...
User Rank: Author
2/8/2019 | 4:50:01 AM
Your only chance of actually controlling network connectivity is by deploying the function inside a VPC and then running a NAT gateway or a virtual firewall on an EC2 instance, but then, you have to deal with a new set of problems, not to mention that you just "de-serverlessed" (I need to trademark this term) the application.
There are alternatives to VPC, especially around outbound networking - you could use a library like FunctionShield (free), which enables you to regain controls over where/who/what the function can communicate with (proper disclosure - my team developed that library). More information on the github project: https://github.com/puresec/FunctionShield/
To your last point - application/business layer security should always remain the responsibility of the application owner, both because of liability, but also because the owner is the only one who really understands the business logic.
FaaS platforms will evolve to be more intelligent and tailored to specific use cases, and together with serverless-native app security solutions and cloud-native mind-set, I'm certain that the overall security posture is about to get a serious boost.