Skip to content

[Critical] Insecure Default Configuration: RCE Risk via UNSANDBOXED Mode & Hardcoded Secrets #373

@A-Isnandar

Description

@A-Isnandar

Vulnerability Description
I have identified critical security misconfigurations in the .env.example file provided in the repository.

  1. Remote Code Execution (RCE) Risk:
    The AP_EXECUTION_MODE is set to "UNSANDBOXED" by default. If a developer or user deploys this application using the default configuration, it exposes the host server to arbitrary code execution risks via workflow automation features.

  2. Hardcoded Cryptographic Secrets:
    Sensitive keys such as AP_API_KEY, AP_ENCRYPTION_KEY, AP_JWT_SECRET, and database credentials are hardcoded with actual values instead of placeholders.

Impact Assessment

  • Critical (RCE): Potential for full server takeover if the execution mode is not sandboxed.
  • High (Data Leak): Hardcoded encryption keys jeopardize the confidentiality of user data and sessions.

Proposed Solution
I have prepared a fix that:

  • Changes the default execution mode to SANDBOXED.
  • Replaces all hardcoded secrets with safe placeholders (e.g., CHANGE_ME_IN_PRODUCTION).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions