Unreleased Resource: Streams

[Sneha0523]

usr/local/share/agentWork/app/App_iOS-2/Pods/FirebaseCrashlytics/Crashlytics/Shared/FIRCLSNetworking/FIRCLSMultipartMimeStreamEncoder.m : 37

The function populateRequest:withDataFromEncoder:() in FIRCLSMultipartMimeStreamEncoder.m sometimes fails to release a system resource allocated by outputStreamToMemory() on line 37.The identified function sometimes fails to release a system resource.

The function lambda { (inout DataStreamRequest.StreamMutableState) -> Void? }() in Request.swift sometimes fails to release a system resource allocated by open() on line 1377.The identified function sometimes fails to release a system resource.

The program can potentially fail to release a system resource. In this case, there are program paths on which the resource allocated in FIRCLSMultipartMimeStreamEncoder.m on line 37 is not released. Resource leaks have at least two common causes:

• Error conditions and other exceptional circumstances.
• Confusion over which part of the program is responsible for releasing the resource.

Most unreleased resource issues result in general software reliability problems. However, if an attacker can intentionally trigger a resource leak, the attacker may be able to launch a denial of service attack by depleting the resource pool.