Bug 99250 - Bluetooth socket left unclosed if connection failed
Summary: Bluetooth socket left unclosed if connection failed
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: Impress Remote
Classification: Unclassified
Component: Android Remote App (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All Android
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-12 17:57 UTC by Vijayaraghavan Murali
Modified: 2018-01-02 10:18 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vijayaraghavan Murali 2016-04-12 17:57:17 UTC
Hi, we're a research team at Rice University working on automatic detection of anomalies in open source Android apps. Our tool was able to detect in the Impress Remote app that the BluetoothSocket "mServerConnection" in the class BluetoothServerConnection.java is left unclosed in the "open()" method in case the connection failed and threw an exception (lines 46-50).

Our tool works by automatically learning API usage specifications from thousands of Android apps, and in this case it learned that when "connect()" called on a BluetoothSocket object throws an exception, it is almost always followed by a "close()" on that object. If not, depending on the state of the socket when the connection failed, it could be left open thereby preventing future requests (possibly by other apps) to use the socket. We could not produce an actual observable bug from this but it is conceivable that this may be exploited if one intends to.

For our research purposes, we would greatly appreciate it if you can provide your comments regarding the nature/severity of this "bug".

Thanks,
Vijay
Comment 1 Xisco Faulí 2017-04-13 09:47:19 UTC Comment hidden (obsolete)
Comment 2 QA Administrators 2017-12-04 12:45:52 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2018-01-02 10:18:42 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20180102