Opened 5 years ago

Closed 4 years ago

#22234 closed Bug (fixed)

Special characters in database password are not escaped correctly on Windows platforms

Reported by:… Owned by: nobody
Component: Core (Management commands) Version: master
Severity: Normal Keywords:
Cc: anubhav9042@… Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


On Windows platforms, the database client command line is composed as a string, but no escaping whatsoever is performed on the parameters. Database configuration can contain special characters (especially the password), which would require escaping.

Real-life case:

Change History (6)

comment:1 Changed 5 years ago by…

Has patch: set
Version: 1.6master

comment:2 Changed 5 years ago by Baptiste Mispelon

Component: Database layer (models, ORM)Core (Management commands)
Triage Stage: UnreviewedAccepted


It seems that the different codepath on windows was added as a result of #10357.

Looking at the discussion (especially comment number 3 [1]), it seems that using subprocess was considered at the time but it wasn't used because it was incompatible with Python 2.3 which was supported at the time.

The patch looks good and cleans things up nicely but I don't have access to a windows box to make sure it actually works.
I'm also concerned about a potential for subtle differences between os.execp and The documentation of os.execp [2] is a bit hard to read and as a result, I can't really tell exactly what differences there are between the two.

Still, I'll mark this ticket as accepted, if only on the basis that using os.system(" ".join(args)) is clearly wrong.



comment:3 Changed 5 years ago by Mihail Milushev

(I'm the reporter of this bug, but forgot to log in when I submitted it)

From the docs:

The full function signature is the same as that of the Popen constructor - this functions passes all supplied arguments directly through to that interface.

From the subprocess.Popen docs:

Execute a child program in a new process. On Unix, the class uses os.execvp()-like behavior to execute the child program. On Windows, the class uses the Windows CreateProcess() function.

Sounds to me and os.execvp are explicitly meant to be compatible on Unix, and on Windows os.execvp isn't an option anyway.

Last edited 5 years ago by Mihail Milushev (previous) (diff)

comment:4 in reply to:  3 Changed 5 years ago by ANUBHAV JOSHI

Cc: anubhav9042@… added

If only you could add a test to your PR, we can test the new implementation.

comment:5 Changed 5 years ago by Mihail Milushev

I would, but I'm not really sure how to approach testing this change. The fact that there are zero existing tests for the DatabaseClient implementations does not help either — it seems historical changes to backends.*.client.DatabaseClient have never included a testcase.

comment:6 Changed 4 years ago by Tim Graham <timograham@…>

Resolution: fixed
Status: newclosed

In bf5382c6e549d78da9f7029cd86686459b52eaed:

Fixed #22234 -- Replaced OS-specific code with in dbshell.

This fixes escaping of special characters on Windows.

Note: See TracTickets for help on using tickets.
Back to Top