In PHP from 8.1.* before 8.1.32, from 8.2.* before 8.2.28, from 8.3.* before 8.3.19, from 8.4.* before 8.4.5, when requesting a HTTP resource using the DOM or SimpleXML extensions, the wrong content-type header is used to determine the charset when the requested resource performs a redirect. This may cause the resulting document to be parsed incorrectly or bypass validations.
The source code contains comments that do not accurately describe or explain aspects of the portion of the code with which the comment is associated.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Php | Php | 8.1.0 (including) | 8.1.32 (excluding) |
| Php | Php | 8.2.0 (including) | 8.2.28 (excluding) |
| Php | Php | 8.3.0 (including) | 8.3.19 (excluding) |
| Php | Php | 8.4.0 (including) | 8.4.5 (excluding) |
| Php7.4 | Ubuntu | focal | * |
| Php8.1 | Ubuntu | jammy | * |
| Php8.3 | Ubuntu | noble | * |
| Php8.3 | Ubuntu | oracular | * |
| Php8.4 | Ubuntu | devel | * |
When a comment does not accurately reflect the associated code elements, this can introduce confusion to a reviewer (due to inconsistencies) or make it more difficult and less efficient to validate that the code is implementing the intended behavior correctly. This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities. It also might make it easier to introduce vulnerabilities.