Skip to content

Site docs: clarify security model #503

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
garydgregory merged 1 commit into from
Jun 17, 2026
+13 −0
Merged

Site docs: clarify security model #503

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions src/site/xdoc/security.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,19 @@
incomplete, please report them privately to the Apache Security Team. Thank you.
</p>
</section>
<section name="Security Model">
<p>The <a href="https://commons.apache.org/security.html#Security_Model">Apache Commons security model</a> specifies
that it is unsafe to pass possibly malicious input to Commons libraries
unless otherwise specified.
For Commons BCEL, processing untrusted class data is supported to the extent that
this should never allow the supplier of the data to trigger arbitrary code execution,
filesystem or network access. It may still trigger other crashes, such as for example <code>StackOverflowError</code> or <code>OutOfMemoryError</code>:
if your code uses BCEL to process untrusted input
then it is up to you to compensate for that as necessary.
Loading or executing the generated classes is unsafe and may cause unexpected behaviour,
including execute arbitrary code execution.
</p>
</section>
<section name="Security Vulnerabilities">
<subsection name="CVE-2022-42920">
<ul>
Expand Down
Loading