PT-2026-42595 · Crates.Io · Onenote Parser
Publicado
2026-05-21
·
Atualizado
2026-05-21
CVSS v3.1
4.4
Média
| Vetor | AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L |
Impact
A maliciously crafted
.onetoc2 table-of-contents file can cause Parser::parse notebook to open arbitrary files on the host filesystem outside the notebook's directory. The parser reads entry names listed inside the .onetoc2 and joins them against the notebook's base directory without validating that they are relative paths confined to that directory.The parser will bail out when the target file fails to parse as a OneNote section, so direct content exfiltration through the parser's return value is not practical, though file-existence probing and denial-of-service via large or special files remain possible.
Anyone using
onenote parser to parse .onetoc2 files received from untrusted sources is affected. Users who only ever parse their own notebooks are not at meaningful risk.Patches
Fixed in onenote parser 1.1.1. The fix rejects absolute paths, parent-directory components, and other invalid path characters in entry names, and additionally canonicalises the resolved path to confirm it stays inside the notebook's base directory.
Workarounds
For users who cannot upgrade to 1.1.1:
- Only call
Parser::parse notebookon.onetoc2files from trusted sources. - Alternatively, use
Parser::parse section/Parser::parse section bufferon individual .one files, which do not perform the directory walk.
Correção
Path traversal
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾
Enumeração de Fraquezas
Identificadores relacionados
Produtos afetados
Onenote Parser