Dinky <=1.2.5 Path Traversal in Git Project Management

Thinking Process: 1. Analyze the Request: Task: Translate a Chinese vulnerability intelligence summary to English. Role: Professional translator specializing in cybersecurity. Format: Maintain all Markdown formatting intact. Constraint: Do not add any introductory or concluding remarks. Just output the English translation. 2. Analyze the Source Text: Title: (Critical Vulnerability Information) Section 1: (Affected Environment) Project: Dinky Repository: URL Affected Versions: -> -> -> -> -> -> -> -> -> -> -> -> -> -> -> -> -> -> -> -> -> -> -> -> -> -> -> (or , is better for fixes) -> -> -> 5. Review and Refine: Check specific terms: "纵深防御" is standardly translated as "Defense in Depth". Check "已认证" in Attack Vector context: "Authenticated" is correct. Check "范围: 不变": In CVSS context, "Unchanged" is the standard term for Scope. Ensure Markdown bolding ( ) is preserved. Ensure list structure is preserved. 6. Final Polish: Make sure the flow is natural in English. "具有Git项目创建权限的攻击者" -> "Attackers with Git project creation privileges" "向服务器文件系统写入任意文件" -> "write arbitrary files to the server filesystem" "可能消耗磁盘空间" -> "consume disk space" "建立持久化机制" -> "establish persistence mechanisms" 7. Final Output Generation (matching the thought process above). Self-Correction on "Remediation": "修复方案" can be "Remediation" or "Mitigation". Given it includes code fixes, "Remediation" is appropriate. Self-Correction on CVSS terms: Ensure standard CVSS terminology (e.g., "Privileges Required" instead of "Required Privileges" though both are understood, CVSS spec uses "Privileges Required"). Self-Correction on "Secondary Trigger Point": "Secondary Trigger Point" is fine, or "Secondary Entry Point". The source says "触发点", so "Trigger Point" is accurate. Let's assemble the final markdown. Wait, check "Lines 143-145" vs "行 143-145". "Lines" is better. Check "Line 86" vs "第 86 行". "Line 86" is better. Check "Remediation" vs "Fix Scheme". "Remediation" is professional. Check "Defense in Depth". Correct. Check "Privileges Required". Correct CVSS term. One small detail: "网络（已认证）" -> "Network (Authenticated)". "所需权限" -> "Privileges Required". "范围" -> "Scope". Looks good. Ready to output.cw Critical Vulnerability Information Affected Environment Project: Dinky Repository: https://github.com/DataLinkDC/dinky Affected Versions: <=1.2.5 Vulnerability Overview The Git project management function of the Dinky platform contains a path traversal vulnerability. Attackers with Git project creation privileges can construct malicious project names containing path traversal sequences (e.g., .../../evil) to write arbitrary files to the server filesystem during project creation or build. Vulnerability Details Vulnerable File: dinky-admin/src/main/java/org/dinky/utils/GitRepository.java Vulnerable Function: getProjectDir(String projectName) (Lines 143-145) Primary Entry Point: GitController.saveOrUpdateGitProject() at Line 86 Secondary Trigger Point: GitController.buildGitProject() at Line 154 Attack Vector: Network (Authenticated) Impact Analysis Confidentiality: Low - Attackers can read sensitive files written to accessible locations Integrity: High - Attackers can write files to arbitrary locations on the server, potentially: - Implant malicious JAR files to execute code - Write configuration files to alter system behavior - Overwrite existing files based on application user privileges - Establish persistence mechanisms Availability: Low - Filesystem operations may consume disk space or interrupt application functionality CVSS v3.1: 7.5 (High) Attack Vector: Network (AV:N) Attack Complexity: Low (AC:L) Privileges Required: Low (PR:L) - Requires Git project creation privileges User Interaction: None (UI:N) Scope: Unchanged (S:U) Confidentiality: Low (C:L) Integrity: High (I:H) Availability: Low (A:L) Remediation 1. Input Validation (Primary Fix): Add strict GitProjectDTO validation 2. Path Validation (Defense in Depth): Use Path.normalize() and validate the resolved path 3. File Permissions: Ensure the Dinky application runs with minimal filesystem privileges to limit potential impact.

Goal Reached Thanks to every supporter — we hit 100%!

Dinky <=1.2.5 Path Traversal in Git Project Management

More from this source