Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Potential information disclosure: runtime Laravel log accessible without authentication in a Docker deployment

未关闭
  • 哪里不对？
#168 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
apache, docker, laravel, php
领域
infrastructure, security

调研方向

Start by comparing the Docker deployment’s effective Apache configuration and persistent application volume with the supplied .htaccess rules, which returned 403 in a separate local test. Reproduce with a harmless marker in storage/logs/laravel.log and an unauthenticated request; first establish the affected image version and deployment configuration. Done means the request is denied in the affected supported configurations and a regression test covers it.

由索引模型根据 Issue 内容生成。

描述

LinkStack version

The exact application version, container image tag, and image digest of the affected deployment have not yet been recorded. The affected version range is therefore unknown.

Description

In my Docker-hosted LinkStack deployment, the runtime Laravel log is accessible over HTTP without authentication at:

/storage/logs/laravel.log

This report concerns the runtime log, not the separate, currently empty assets/storage/logs/laravel.log file included in the source repository.

Application logs should not be publicly downloadable. Depending on the exceptions and logging configuration, they may disclose stack traces, internal filesystem paths, database error details, or sensitive values included in exception messages. No credentials or personal data are included in this report.

The precise cause in the affected deployment has not yet been established. Possible causes include ineffective access-denial rules, deployment-specific configuration, or an older application directory persisted in a Docker volume. This report does not establish that every official image or a fresh installation is affected.

Details about your system
  • Deployment: Docker-hosted LinkStack
  • Observed behavior: unauthenticated HTTP access to /storage/logs/laravel.log
  • Exact image repository, tag, and digest: not yet recorded
  • LinkStack version, PHP version, Docker Compose configuration, and reverse-proxy configuration: not yet provided
How to reproduce

The following describes the reported behavior on the affected deployment; reproduction on a clean official image is still pending.

  1. Use a controlled LinkStack test deployment matching the affected configuration.

  2. Ensure storage/logs/laravel.log exists and contains only a harmless test marker. Do not use production log contents.

  3. From an unauthenticated client, request:

    curl -i 'https://<test-instance>/storage/logs/laravel.log'

  4. Check whether the response exposes the marker.

Expected behavior: The request is denied or the file is not web-accessible, regardless of authentication state.

Reported actual behavior: The log file can be retrieved without authentication.

Validation performed so far: A separate local Apache test using the current application checkout returned 403 Forbidden when the supplied .htaccess rules were enabled. This verifies those rules under that configuration, but is not a reproduction of the affected Docker deployment.

Possible Solution
  • Verify that the container’s effective web-server configuration denies access to runtime logs and other private application directories.
  • Apply the protection consistently to HTTP and HTTPS virtual hosts and supported deployment configurations.
  • Add a regression test that creates a harmless runtime log marker and verifies that an unauthenticated request cannot retrieve it.
  • Document how existing installations with persistent application volumes receive updated access-control rules.
  • Longer term, serve only public application files from the document root rather than relying on deny rules to protect internal files.
Additional Context

Related architectural discussion:
https://github.com/LinkStackOrg/LinkStack/issues/935

That issue discusses separating public files from private application files and the limitations of .htaccess on other web servers. It does not specifically document this runtime-log exposure in Docker.

主要语言
Shell
星标
527
派生
72
30 天内没有已合并 PR

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

LinkStackOrg/linkstack-docker 的其他 Issue

查看 LinkStackOrg/linkstack-docker 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。