29 lines
948 B
Markdown
29 lines
948 B
Markdown
 
|
# How Integer Overflow happens in C++ image processing and how to fix it
|
||
|
|
|
||
|
|
## Metadata
|
||
|
|
|
||
|
|
| Field | Value |
|
||
|
|
|---|---|
|
||
|
|
| Institute | Molodetz Institute — Research & Retrieval Division |
|
||
|
|
| Subject | safe-cpp-practices |
|
||
|
|
| Document type | Source Citation Card |
|
||
|
|
| Tier | 2 |
|
||
|
|
| Source title | How Integer Overflow happens in C++ image processing and how to fix it |
|
||
|
|
| Source URL | https://orbisappsec.com/blog/how-integer-overflow-happens-in-c-image-processing-and-how-to-fix |
|
||
|
|
| Source type | blog post |
|
||
|
|
| Date researched | 2026-10-27 |
|
||
|
|
| Researched by | tai (agent), model: Claude Opus 4.8, on behalf of retoor |
|
||
|
|
| Research method | Search aggregator result listing (not independently opened or quoted) |
|
||
|
|
| Confidence | Not independently verified |
|
||
|
|
| Status | Active |
|
||
|
|
|
||
|
|
## Why it's here
|
||
|
|
|
||
|
|
Real signed-int-product-into-size_t allocation bug and its fix.
|
||
|
|
|
||
|
|
## Changelog
|
||
|
|
|
||
|
|
| Date | Change |
|
||
|
|
|---|---|
|
||
|
|
| 2026-10-27 | Logged as consulted-but-not-analyzed. |
|