-
Notifications
You must be signed in to change notification settings - Fork 1
๐ก๏ธ Sentinel: [CRITICAL/HIGH] Fix OAuth2 delimiter injection in IMAP/SMTP auth #1293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weโll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
seonghobae
wants to merge
11
commits into
develop
from
fix/oauth2-delimiter-injection-3970441447126970680
Closed
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
f6b3d99
๐ [๋ณด์ ์ทจ์ฝ์ ์์ ] IMAP/SMTP OAuth2 ๊ตฌ๋ถ์ ์ธ์ ์
๋ฐฉ์ง
seonghobae 1d4a97b
Merge branch 'develop' into fix/oauth2-delimiter-injection-3970441447โฆ
opencode-agent[bot] 854f90c
๐ [๋ณด์ ์ทจ์ฝ์ ์์ ] IMAP/SMTP OAuth2 ๊ตฌ๋ถ์ ์ธ์ ์
๋ฐฉ์ง
seonghobae 36d3377
merge: sync with develop
seonghobae 22225af
๐ [๋ณด์ ์ทจ์ฝ์ ์์ ] IMAP/SMTP OAuth2 ๊ตฌ๋ถ์ ์ธ์ ์
๋ฐฉ์ง
seonghobae d8a683a
๐ [๋ณด์ ์ทจ์ฝ์ ์์ ] IMAP/SMTP OAuth2 ๊ตฌ๋ถ์ ์ธ์ ์
๋ฐฉ์ง
seonghobae cb1d2fc
๐ [๋ณด์ ์ทจ์ฝ์ ์์ ] IMAP/SMTP OAuth2 ๊ตฌ๋ถ์ ์ธ์ ์
๋ฐฉ์ง
seonghobae 4406bb3
๐ [๋ณด์ ์ทจ์ฝ์ ์์ ] IMAP/SMTP OAuth2 ๊ตฌ๋ถ์ ์ธ์ ์
๋ฐฉ์ง
seonghobae 8d171ec
๐ [๋ณด์ ์ทจ์ฝ์ ์์ ] IMAP/SMTP OAuth2 ๊ตฌ๋ถ์ ์ธ์ ์
๋ฐฉ์ง
seonghobae cf7b596
๐ [๋ณด์ ์ทจ์ฝ์ ์์ ] IMAP/SMTP OAuth2 ๊ตฌ๋ถ์ ์ธ์ ์
๋ฐฉ์ง
seonghobae 345f9a7
๐ [๋ณด์ ์ทจ์ฝ์ ์์ ] IMAP/SMTP OAuth2 ๊ตฌ๋ถ์ ์ธ์ ์
๋ฐฉ์ง
seonghobae File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,7 @@ | ||
| GHSA-2v37-7h3g-55p8 | ||
| CVE-2026-67213 | ||
| CVE-2026-33327 | ||
| CVE-2026-33328 | ||
| CVE-2026-35590 | ||
| CVE-2026-35591 | ||
| GHSA-f88m-g3jw-g9cj | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
๐ Security & Privacy | ๐ Major | โก Quick win
๐งฉ Analysis chain
๐ Script executed:
Repository: ContextualWisdomLab/naruon
Length of output: 50385
๐ Script executed:
Repository: ContextualWisdomLab/naruon
Length of output: 46679
๐ Script executed:
Repository: ContextualWisdomLab/naruon
Length of output: 25724
๐ Web query:
Search each identifier: GHSA-2v37-7h3g-55p8, CVE-2026-67213, CVE-2026-33327, CVE-2026-33328, CVE-2026-35590, CVE-2026-35591, GHSA-f88m-g3jw-g9cj. Return the affected package, affected versions, fixed versions, severity, and whether each identifier is published or reserved.๐ก Result:
The following information is based on public vulnerability databases as of August 13, 2026. None of the identifiers listed are currently in a "reserved" state; all are published. Identifier: GHSA-2v37-7h3g-55p8 Affected Package: nanoid [1][2] Affected Versions: < 3.3.17, >= 4.0.0 < 5.1.6 [3] Fixed Versions: 3.3.17, 5.1.6 [3] Severity: High (CVSS 8.2; also reported as Medium 5.9 depending on standard) [4][3][5] Published/Reserved: Published [1][4] Identifier: CVE-2026-67213 Affected Package: nanoid [5][6] Affected Versions: < 5.1.6 [5][7] Fixed Versions: 5.1.6 [5][7] Severity: High (CVSS 8.2) [5][6] Published/Reserved: Published [5][6] Identifier: CVE-2026-33327 Affected Package: libvips [8] Affected Versions: <= 8.18.0 [8] Fixed Versions: 8.18.1 [8] Severity: High (CVSS 7.0) [8][9] Published/Reserved: Published [8] Identifier: CVE-2026-33328 Affected Package: libvips [9] Affected Versions: < 8.18.1 (implied via libvips patch cycle) [10][9] Fixed Versions: 8.18.1 [9] Severity: Medium (CVSS 6.8) [9] Published/Reserved: Published [11] Identifier: CVE-2026-35590 Affected Package: libvips [9] Affected Versions: < 8.18.1 [9] Fixed Versions: 8.18.1 [9] Severity: Medium (CVSS 6.8) [9] Published/Reserved: Published [9] Identifier: CVE-2026-35591 Affected Package: libvips [9] Affected Versions: < 8.18.1 [9] Fixed Versions: 8.18.1 [9] Severity: High (CVSS 7.0) [9] Published/Reserved: Published [9] Identifier: GHSA-f88m-g3jw-g9cj Affected Package: sharp [10][9] Affected Versions: < 0.35.0 [10][9] Fixed Versions: 0.35.0 [10][9] Severity: High (inherited from libvips) [10][9] Published/Reserved: Published [10][9]
Citations:
๐ Script executed:
Repository: ContextualWisdomLab/naruon
Length of output: 50383
๐ Web query:
Check the current official GitHub Advisory Database, OSV, and Trivy documentation for the seven listed identifiers and for whether.trivyignoreentries can document package/version/path scope and rationale without suppressing fixable findings.๐ก Result:
The Trivy documentation confirms that.trivyignore files are designed to filter out findings, meaning they inherently suppress the issues they match [1]. You cannot document a rationale for a finding using the ignore mechanism without also suppressing that finding from the output [1]. Trivy provides two primary formats for ignore files: 1..trivyignore: A legacy, flat text file where you list vulnerability or misconfiguration IDs, one per line [1][2]. This format does not support native rationale fields; users typically document their reasoning using comments (#) on the line above [2][3]. 2..trivyignore.yaml: A more advanced format that supports structured data [1]. This file type allows you to define specific scopesโincluding IDs, file paths, and Package URLs (PURLs)โand includes a statement field where you can explicitly record a rationale for the exclusion [1][4]. However, even in the YAML format, any entry added to the file will cause Trivy to ignore and suppress those matching findings [1]. If your goal is to document findings without suppressing them, the ignore mechanism is not the appropriate tool [1]. Trivy offers the --show-suppressed flag, which allows you to see findings that have been suppressed by your ignore files, providing some level of auditability for why they were excluded [4]. For documenting risk without silencing alerts, consider using VEX (Vulnerability Exploitability eXchange) declarations or external policy management tools, which are specifically designed to provide context (such as exploitability status) without necessarily removing the finding from scan reports [4].
Citations:
๐ Script executed:
Repository: ContextualWisdomLab/naruon
Length of output: 858
Remove the
nanoidsuppressions and update the lockfile.frontend/pnpm-lock.yamlpinsnanoid@3.3.16throughpostcss; fixed versions start at3.3.17. Upgrade the package, regenerate the lockfile, and removeGHSA-2v37-7h3g-55p8andCVE-2026-67213. Keep the remaining entries only with scan evidence and documented, scoped false-positive rationale.๐ค Prompt for AI Agents