Running interpreterInfo.py with non-specified python executables?

Environment data

• Language Server version: 0.5.31.0
• OS and version: CentOS7
• Python version (& distribution if applicable, e.g. Anaconda): Python 3.6

Behaviour

In atop I’m seeing lots of lines like this; note the python3.4:

  2897     - S   0% /home/mroos/.vscode-server/extensions/ms-python.python-2020.2.63990/languageServer.0.5.31/Microsoft.Python.LanguageServer
 2648     - S   0% /usr/bin/python3.4 /home/mroos/.vscode-server/extensions/ms-python.python-2020.2.63990/pythonFiles/interpreterInfo.py
 2657     - S   0% /usr/bin/python3.4 /home/mroos/.vscode-server/extensions/ms-python.python-2020.2.63990/pythonFiles/interpreterInfo.py
 2666     - S   0% /bin/python3.4 /home/mroos/.vscode-server/extensions/ms-python.python-2020.2.63990/pythonFiles/interpreterInfo.py

python3.4 is not installed, but is on my path. (It’s symlinked to something that installs python3.4 as part of an internal tool)

python3.4 isn’t resolved from which python, which python2, which python3. Further, I defined python.pythonPath as a python in a venv.

Any idea how the extension is finding python3.4 and attempting to run interpreterInfo.py?

Logs

User belongs to experiment group 'ShowPlayIcon - start'
User belongs to experiment group 'DebugAdapterFactory - experiment'
User belongs to experiment group 'PtvsdWheels37 - experiment'
User belongs to experiment group 'LS - enabled'
User belongs to experiment group 'UseTerminalToGetActivatedEnvVars - control'
User belongs to experiment group 'WebHostNotebook - control'
> conda --version
> pyenv root
> python3.7 -c "import sys;print(sys.executable)"
> python3.6 -c "import sys;print(sys.executable)"
> python3 -c "import sys;print(sys.executable)"
> python2 -c "import sys;print(sys.executable)"
> python -c "import sys;print(sys.executable)"
> ~/workspace/corpfin/.venv/bin/python3 -c "import sys;print(sys.executable)"
> conda info --json
> conda env list

[karthiknadig]

Extension will use the binary pointed to by pythonpath to run your code or other tools. But it will search the OS for other versions.

If the python* in /bin/ or /usr/bin/ is replaced with something malicious. At that point a simple ~/.bashrc or the one that conda installs or even doing npm install that installs some native module will trigger that. Something as simple as opening a terminal (outside of VS Code) might be enough to run the malicious code. This is all even before getting to VS Code, let alone the python extension.

[jakebailey]

Transferring to the extension, this is a question about extension interpreter selection.