access controls

[evaril]

---

Notes

Initial Security Analysis — Snap: python-ai-toolkit

1. 📦 Observed Behavior
   Snap Executable Chain:
   systemd → jupyter.wrapper (PID 1732) → python3 jupyter-lab (PID 1818)
   Command-line execution:

   python3 /snap/python-ai-toolkit/41/bin/jupyter-lab
   --allow-root
   --no-browser
   --ip=0.0.0.0
   --NotebookApp.token=
   --NotebookApp.password=
   --NotebookApp.base_url=jupyter

    No authentication enabled
    World-accessible interface (0.0.0.0)
    Launches as root
   

   Environment Variables:
   SNAP_USER_DATA=/root/snap/...
   SNAP_COOKIE, SNAP_INSTANCE_KEY, and SNAP_CONTEXT suggest auto-launched instance with full Snap confinement
   LD_LIBRARY_PATH extended with multiple custom and Snap-controlled lib directories
   XDG_RUNTIME_DIR=/run/user/0/snap.python-ai-toolkit — confirms root context snap runtime

   Observed Network Behavior:
   Connections attempted to:
   185.125.188.58 and .59: Canonical infrastructure
   91.189.95.24: Ubuntu updates/CDN mirror
   Some were rejected (RST packets), suggesting unexpected outbound behavior

   Filesystem Observations:
   Runs from /snap/python-ai-toolkit/41/
   Drops configurable content in /var/snap/... and /root/snap/...
   References to NotebookApp, nbdime, async-ua, ua-subscribe, and DefCupWrapper

2. 🚨 Security Concerns
   Threat Description Severity
   🔓 Unauthenticated Remote Access Jupyter launched on 0.0.0.0 without token or password Critical
   🧱 AppArmor ptrace Denials Indicates unconfined behavior attempts, often privilege probes High
   🧩 Custom Library Paths Custom .so preload chains from Snap could be used for DLL injection or sandbox escapes High
   📡 Unexpected Network Traffic Repeated attempts to Canonical over HTTPS (RST returned) Medium
   👤 Root Execution Context Entire application is running as root, increasing impact potential Critical