On http://httpd.apache.org/docs/2.2/logs.html
Anyone who can write to the directory where Apache is writing a log file can almost certainly gain access to the uid that the server is started as, which is normally root. Do NOT give people write access to the directory the logs are stored in without being aware of the consequences; see the security tips document for details
How does this work? How does writing to a file that Apache is also writing to grant access to the Apache Parent Process user (root)?
Check out the security tips page.
http://httpd.apache.org/docs/2.2/misc/security_tips.html
Since apache opens and reads the log file as root, there is a danger here for abuse. Not sure why you would want a non-root (apache) user to have write access to the files. You can safely grant read access but would suggest that write access only be given to old files that have rotated. Apache is not opening these files when you use logrotate to manage log rotation.
If apache is running as root... and a non-root user writes a script for apache to execute... then by-virtue of how processes work... the script runs as root. As a security measure, most distributions do not run apache as root... but as a dedicated user like "www-data" or "apache" or "httpd".