passlib trunc_password MAX_PASSWORD_LENGTH password truncation
Bug #1175904 reported by
Kurt Seifried
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Li Ma |
Bug Description
Grant Murphy originally reported:
* Insecure / bad practice
The trunc_password function attempts to correct and truncate passwords
that are over the MAX_PASSWORD_LENGTH value (default 4096). As the
MAX_
to restrict all passwords to length = 1. This scenario might be unlikely
but generally speaking we should not try to 'fix' invalid input and
continue on processing as if nothing happened.
If this is exploitable it will need a CVE, if not we should still harden it so it can't be monkeyed with in the future.
information type: | Private Security → Public |
Changed in keystone: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in keystone: | |
assignee: | nobody → Li Ma (nick-ma-b) |
Changed in keystone: | |
assignee: | Li Ma (nick-ma-b) → nobody |
Changed in keystone: | |
assignee: | nobody → Li Ma (nick-ma-z) |
Changed in keystone: | |
milestone: | none → juno-2 |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | juno-2 → 2014.2 |
To post a comment you must log in.
I don't see this as exploitable, as you'd have to run arbitrary Python code within the Keystone server, at which point there are funnier things to do than altering the max password length.
Agree that we could strengthen that part to avoid it being monkeyed with in the future. With your permission, I'd open this bug publicly and let it be strengthened in public patches.