A Django App

Its Layers

This is a Python app. nginx takes the requests and passes them to Gunicorn, which runs Django, and the app keeps its data in PostgreSQL.

The stack runs from the top layer down, as on the topic page. Each layer shows its technology, and the badge beside it says who runs and patches it.

Who Runs What

You run every layer shown, from Django, Gunicorn and nginx to Python, PostgreSQL and Linux. A managed database service can take PostgreSQL off your hands, and on a cloud virtual machine the provider runs only the hypervisor and the hardware beneath Linux.

You

Your team runs it and installs its updates.

Where Its Code Comes From

Django, Gunicorn and the app's other packages come from PyPI. The server's own software, nginx included, comes from the Linux distribution's packages, and a build pipeline puts the app together.

• PyPI
• OS Packages
• CI and Build Systems

Well-Known Flaws in Its Layers

These are well-known flaws in the technologies this stack is built from. Each CVE id links to its advisory, and the technology's own page says how far that flaw reached.

• CVE-2016-5195 (opens in a new tab)2016

  Dirty COW, in Linux

  A race condition in the Linux kernel let a local user gain root.

Sources

• Microsoft Learn: shared responsibility in the cloud (opens in a new tab)
• Django documentation: how to use Django with Gunicorn (opens in a new tab)