CVE-2023-38152

Controls whether organization resources are exposed to external system spheres by permitting or prohibiting their use.

The control ensures information is not released into a security sphere where the recipient lacks matching access authorizations.

The control ensures information resources are not exposed to the incorrect (public) sphere through review and authorization.

Protects against data mining that would expose resources to unauthorized spheres by enforcing detection and controls.

Restricts information flows to ensure resources are not exposed to incorrect or unauthorized spheres.

Controlling internal connections prevents exposure of resources to unintended internal spheres.

Knowing exact processing and storage locations helps avoid exposure of resources to incorrect spheres.

The control prevents exposure of the media resource to the wrong security sphere.

Vulnerability identification processes can discover buffer over-read flaws via scanning or review.

Network segmentation and unauthorized-access protections reduce the chance of resources being reachable by the wrong sphere.

Patching or replacing vulnerable software removes known instances of buffer over-read bugs.

Placing systems of differing trust levels into separate domains prevents resources from being placed in a sphere where they are reachable by unintended actors.

Secure SDLC mandates input validation and bounds checking that can prevent buffer over-reads.

Application security requirements can specify buffer-size and bounds-checking rules.

Secure architecture principles include memory-safety and bounds-checking design choices.

Secure coding standards directly require bounds-checked buffer access, mitigating over-reads.