The kramdown gem before 2.3.0 for Ruby processes the template option inside Kramdown documents by default, which allows unintended read access (such as template=/etc/passwd) or unintended embedded Ruby code execution (such as a string that begins with template=string://<%= `). NOTE: kramdown is used in Jekyll, GitLab Pages, GitHub Pages, and Thredded Forum.
Weakness
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Kramdown |
Kramdown_project |
* |
2.3.0 (excluding) |
| Ruby-kramdown |
Ubuntu |
bionic |
* |
| Ruby-kramdown |
Ubuntu |
devel |
* |
| Ruby-kramdown |
Ubuntu |
esm-apps/bionic |
* |
| Ruby-kramdown |
Ubuntu |
esm-apps/focal |
* |
| Ruby-kramdown |
Ubuntu |
esm-apps/jammy |
* |
| Ruby-kramdown |
Ubuntu |
esm-apps/noble |
* |
| Ruby-kramdown |
Ubuntu |
esm-apps/xenial |
* |
| Ruby-kramdown |
Ubuntu |
focal |
* |
| Ruby-kramdown |
Ubuntu |
groovy |
* |
| Ruby-kramdown |
Ubuntu |
hirsute |
* |
| Ruby-kramdown |
Ubuntu |
impish |
* |
| Ruby-kramdown |
Ubuntu |
jammy |
* |
| Ruby-kramdown |
Ubuntu |
kinetic |
* |
| Ruby-kramdown |
Ubuntu |
lunar |
* |
| Ruby-kramdown |
Ubuntu |
mantic |
* |
| Ruby-kramdown |
Ubuntu |
noble |
* |
| Ruby-kramdown |
Ubuntu |
oracular |
* |
| Ruby-kramdown |
Ubuntu |
plucky |
* |
| Ruby-kramdown |
Ubuntu |
trusty |
* |
| Ruby-kramdown |
Ubuntu |
xenial |
* |
Potential Mitigations
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries.
- Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
- For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.
- One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
References