提交 #884184: Node.js @alifd/next 1.27.34 Prototype Pollution

A prototype pollution vulnerability exists in @alifd/next 1.27.34.
The affected package exposes locale and configuration merging logic through ConfigProvider. ConfigProvider.getContextProps(props, displayName) accepts locale/config input and calls an internal deepMerge helper with user-controlled data. The helper recursively merges object properties without rejecting dangerous keys such as proto, constructor, or prototype.
When a crafted locale/config object contains an own proto property, the merge operation can resolve target["proto"] to Object.prototype and write attacker-controlled properties globally. This pollutes Object.prototype and may cause later plain objects to inherit unexpected properties.
The issue is reachable through public configuration paths including component locale props, ConfigProvider locale context, ConfigProvider.setLocale(), ConfigProvider.initLocales(), and static component APIs that call ConfigProvider.getContextProps.
Affected version:
@alifd/next 1.27.34
Impact:
Prototype pollution through public UI configuration / locale merge APIs. Exploitability depends on applications loading untrusted or partially trusted locale, tenant branding, remote UI config, or component configuration into Fusion Next.
Recommended fix:
Reject __proto__, constructor, and prototype keys before reading or writing dynamic merge keys. Use own-property checks and avoid recursively merging into inherited prototype objects.

• 来源: ⚠️ https://github.com/alibaba-fusion/next/issues/5101
• 用户: wjm3 (UID 99672)
• 提交: 2026-07-09 14時58分 (2 月前)
• 管理: 2026-08-23 18時04分 (2 months later)
• 状态: 已接受
• VulDB条目: 394564 [alibaba-fusion next 直到 1.27.34 deepMerge index.tsx ConfigProvider.getContextProps locale 远程代码执行]
• 积分: 20