Why can C programs be more prone to buffer-overflow vulnerabilities, according to the material?

### Why this is right C gives programmers direct access to memory through pointers and does not automatically check that array accesses remain within bounds. Errors in size handling can therefore overwrite neighboring memory. ### The concept A buffer-overflow risk often begins with incorrect assumptions about input length. The material recommends checking buffer, string, and array sizes, using appropriate library functions, or choosing memory-safe languages such as C#, Python, or JavaScript. ### The other options - **C always encrypts data before storing it**: encryption is unrelated to automatic bounds checking. - **C cannot run on operating systems**: C is commonly used for system software. - **C prevents programs from using arrays**: C supports arrays, but does not automatically enforce their bounds. ### Terms - **Pointer**: a value referring to a memory location. - **Bounds checking**: checking that an operation stays within an allowed memory range. ### Remember Direct memory control increases the need for careful size checks.