Files
ragflow/internal/cpp
OrbisAI Security f17a66d4f0 fix: the opencc c library uses fgets() to read dicti... in text.c (#13970)
## Summary
Fix critical severity security issue in
`internal/cpp/opencc/dictionary/text.c`.

## Vulnerability
| Field | Value |
|-------|-------|
| **ID** | V-001 |
| **Severity** | CRITICAL |
| **Scanner** | multi_agent_ai |
| **Rule** | `V-001` |
| **File** | `internal/cpp/opencc/dictionary/text.c:107` |

**Description**: The OpenCC C library uses fgets() to read dictionary
and configuration files without proper bounds validation on subsequent
buffer operations. While fgets() itself is bounds-checked, the sprintf()
call at config_reader.c:174 constructs file paths by concatenating
home_path and filename without verifying the result fits in pkg_filename
buffer. An attacker providing malformed OpenCC configuration files with
excessively long path components can overflow the fixed-size buffer,
overwriting adjacent memory including return addresses and function
pointers.

## Changes
- `internal/cpp/opencc/config_reader.c`
- `internal/cpp/opencc/dictionary/text.c`
- `internal/cpp/opencc/utils.c`

## Verification
- [x] Build passes
- [x] Scanner re-scan confirms fix
- [x] LLM code review passed

---
*Automated security fix by [OrbisAI Security](https://orbisappsec.com)*


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Bug Fixes**
* Improved error detection and handling for malformed configuration and
dictionary entries during file parsing.
* Enhanced memory cleanup in error recovery paths to prevent potential
issues.
* Strengthened robustness of string operations and buffer handling
throughout the library.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Co-authored-by: Ubuntu <ubuntu@ip-172-31-32-15.us-west-2.compute.internal>
2026-05-19 13:55:33 +08:00
..
2026-03-04 19:17:16 +08:00
2026-03-04 19:17:16 +08:00
2026-03-04 19:17:16 +08:00
2026-03-04 19:17:16 +08:00
2026-03-04 19:17:16 +08:00
2026-03-04 19:17:16 +08:00
2026-03-04 19:17:16 +08:00
2026-03-04 19:17:16 +08:00
2026-03-04 19:17:16 +08:00
2026-03-09 17:48:29 +08:00
2026-03-04 19:17:16 +08:00
2026-03-04 19:17:16 +08:00
2026-03-23 15:40:35 +08:00
2026-03-23 15:40:35 +08:00
2026-03-04 19:17:16 +08:00
2026-03-04 19:17:16 +08:00
2026-03-04 19:17:16 +08:00
2026-03-04 19:17:16 +08:00
2026-03-04 19:17:16 +08:00