Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Not Evaluated
-
Resolution: Duplicate
-
Affects Version/s: 5.3.2
-
Fix Version/s: None
-
Component/s: Core: Other
-
Labels:None
Description
It appears that the first entry in QCoreApplication::libraryPaths() is the path to Qt installation directory on the build machine. For example, on my machine this is C:/Qt/5.3/msvc2013_64_opengl/plugins.
Is this a security risk? What happens if I create a malicious DLL named C:/Qt/5.3/msvc2013_64_opengl/plugins/qwindows.dll on a target machine which happens to run my application?
Attachments
Issue Links
- duplicates
-
QTBUG-15234 Qt hard-codes paths in libraries/binaries
-
- Closed
-