Help Center

Improved

Fixed

base44

In Review

Planned

In Progress

Completed

Rejected

High Priority

Low Priority

The official Base44 roadmap - submit ideas, upvote features and track what’s planned. The content outlines Base44’s general product direction for informational purposes only. It is not a commitment to deliver any features or functionality and should not be relied on for purchasing decisions. All items are subject to change at Base44’s sole discretion.

Backlog

Next up

Done

Feature Roadmap

This is the Base44 Integration Roadmap. Suggest and upvote integrations you'd like to see supported in our platform. Whether it's a data source, plugin, or workflow tool — your input helps guide what we build next. Follow along to track upcoming, active, and recently added integrations!

Future Requests

Integration Roadmap

Hey {name|there}! 👋

Hi Base44 Security Team,I am writing to responsibly disclose a critical security vulnerability I discovered within the Base44 agent runtime environment.Vulnerability Type: Local File Inclusion (LFI) / Information Disclosure Severity: Critical Status: UnpatchedSummary: While testing the agent environment, I discovered that it is possible to bypass file-read restrictions to access sensitive system files, specifically <code>/proc/self/environ</code>. This file exposes high-privilege credentials and internal infrastructure details.Sensitive Data Exposed: Through this vulnerability, I have successfully retrieved:<ul><li>AWS Secret Access Keys: Providing potential access to S3 buckets (<code>base44-app-archives</code>, <code>base44-app-repositories</code>).</li><li>BASE44_SERVICE_TOKEN: A JWT that appears to allow service-level impersonation.</li><li>Infrastructure Metadata: Details regarding the gVisor runtime and Oracle Cloud (OCI) deployment in the <code>eu-frankfurt-1</code> region.</li></ul>Proof of Concept (PoC): The vulnerability exists in the handling of file uploads/reads within the Gradio-based API. By crafting a multipart form request that points to system paths, the server returns the contents of internal files.I have attached a truncated log of the leaked environment variables to this email as proof. I have the full logs and the specific script used to reproduce this and can provide them upon request.Recommendation:<ol><li>Secret Rotation: Immediately rotate all AWS keys and Service Tokens exposed in the environment.</li><li>Path Sanitization: Implement strict validation on all file paths in the <code>gradio_api</code> to prevent traversal (e.g., blocking <code>/proc/</code>, <code>/etc/</code>, and <code>../</code>).</li><li>Principle of Least Privilege: Ensure the containerized process does not run as <code>root</code> and does not have direct access to sensitive environment variables unless absolutely necessary.</li></ol>I look forward to your confirmation of this report and details regarding your bug bounty process.Best regards,Tahir Rasoollinkedin: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://www.linkedin.com/in/tahir-rasool-13617a373/">https://www.linkedin.com/in/tahir-rasool-13617a373/</a>

Halo Tim Keamanan Base44,Saya menulis surat ini untuk secara bertanggung jawab melaporkan kerentanan keamanan kritis yang saya temukan di lingkungan runtime agen Base44.Jenis Kerentanan: Local File Inclusion (LFI) / Pengungkapan Informasi Tingkat Keparahan: Kritis Status: Belum DitambalRingkasan: Saat menguji lingkungan agen, saya menemukan bahwa pembatasan pembacaan file dapat dilewati untuk mengakses file sistem yang sensitif, khususnya <code>/proc/self/environ</code>. File ini memaparkan kredensial dengan hak akses tinggi dan detail infrastruktur internal.Data Sensitif yang Terungkap: Melalui kerentanan ini, saya berhasil memperoleh:<ul><li>Kunci Akses Rahasia AWS: Memberikan akses potensial ke bucket S3 (<code>base44-app-archives</code>, <code>base44-app-repositories</code>).</li><li>BASE44_SERVICE_TOKEN: JWT yang tampaknya memungkinkan peniruan identitas tingkat layanan.</li><li>Metadata Infrastruktur: Detail mengenai runtime gVisor dan penyebaran Oracle Cloud (OCI) di wilayah <code>eu-frankfurt-1</code>.</li></ul>Bukti Konsep (PoC): Kerentanan ini terdapat dalam penanganan unggahan/pembacaan file di dalam API berbasis Gradio. Dengan membuat permintaan formulir multipart yang mengarah ke jalur sistem, server akan mengembalikan isi file internal.Saya telah melampirkan log terpotong dari variabel lingkungan yang bocor ke email ini sebagai bukti. Saya memiliki log lengkap dan skrip spesifik yang digunakan untuk mereproduksi ini dan dapat menyediakannya atas permintaan.Rekomendasi:<ol><li>Rotasi Rahasia: Segera lakukan rotasi semua kunci AWS dan Token Layanan yang terpapar di lingkungan.</li><li>Sanitasi Jalur: Terapkan validasi ketat pada semua jalur file di <code>gradio_api</code> untuk mencegah traversal (misalnya, memblokir <code>/proc/</code>, <code>/etc/</code>, dan <code>../</code>).</li><li>Prinsip Hak Akses Terbatas: Pastikan proses yang dikontainerisasi tidak berjalan sebagai <code>root</code> dan tidak memiliki akses langsung ke variabel lingkungan sensitif kecuali benar-benar diperlukan.</li></ol>Saya menantikan konfirmasi Anda mengenai laporan ini dan detail mengenai proses bug bounty Anda.Salam hormat,Tahir Rasoollinkedin: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://www.linkedin.com/in/tahir-rasool-13617a373/">https://www.linkedin.com/in/tahir-rasool-13617a373/</a>

PENTING: Terpaparnya Data Sensitif &amp; Kerentanan LFI di Lingkungan Agen Base44

CRITICAL: Sensitive Data Exposure & LFI Vulnerability in Base44 Agent Environment

Tahir Rasool

Base44

CRITICAL: Sensitive Data Exposure & LFI Vulnerability in Base44 Agent Environment

Subscribe to post

Subscribe to post