amoeba commented on issue #5036: URL: https://github.com/apache/arrow-adbc/issues/5036#issuecomment-6925091395
See https://cwiki.apache.org/confluence/spaces/SECURITY/pages/308153000/Documenting+your+security+model See the Arrow monorepo's issue on this: https://github.com/apache/arrow/issues/48559 I thought [this bit ](https://www.postgresql.org/support/security/#:~:text=The%20PostgreSQL%20Security,is%20by%20design.)from the PostgreSQL page on security to be helpful when thinking about what we might say about ADBC drivers: > A security vulnerability in PostgreSQL is an issue that allows a user to gain access to privileges or data that they do not have permission to use, or allows a user to execute arbitrary code through a PostgreSQL process. > The PostgreSQL Security Team does not consider reports on actions a PostgreSQL superuser takes to be a security vulnerability. However, a report on an unprivileged user escalating to superuser generally qualifies as valid. If one of the drivers can be used to either escalate or execute arbitrary code on the server, I think we'd consider that a vulnerability. Beyond that, I think our trust boundary could be "connect only to trusted sources". -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
