PT0-002 · Question #76
Which of the following describe the GREATEST concerns about using third-party open-source libraries in application code? (Choose two.)
The correct answer is A. The libraries may be vulnerable C. The libraries' code bases could be read by anyone. The primary concerns with using third-party open-source libraries in applications are potential security vulnerabilities and the transparency of their code allowing anyone to review it.
Question
Which of the following describe the GREATEST concerns about using third-party open-source libraries in application code? (Choose two.)
Options
- AThe libraries may be vulnerable
- BThe licensing of software is ambiguous
- CThe libraries' code bases could be read by anyone
- DThe provenance of code is unknown
- EThe libraries may be unsupported
- FThe libraries may break the application
How the community answered
(30 responses)- A77% (23)
- B3% (1)
- D13% (4)
- F7% (2)
Why each option
The primary concerns with using third-party open-source libraries in applications are potential security vulnerabilities and the transparency of their code allowing anyone to review it.
Open-source libraries, like any software, can contain undiscovered security vulnerabilities, which, if exploited, could compromise the application using them. Developers must actively monitor for disclosed vulnerabilities in their dependencies.
While licensing can be complex and a legal concern, it's generally a compliance issue rather than a greatest security concern compared to direct vulnerabilities.
The fact that open-source codebases can be read by anyone is both a strength (for auditing) and a significant concern for security, as it facilitates malicious actors in finding and exploiting vulnerabilities. This transparency directly aids attackers in understanding potential weak points.
Unknown provenance (origin) is related to security and trustworthiness but is often addressed through community vetting and repository reputation, whereas known vulnerabilities and the openness that aids attackers are more direct threats.
Lack of support is a maintenance and reliability concern, but not typically a security concern as great as active vulnerabilities or the inherent transparency of open-source code to attackers.
Libraries breaking an application is a functional and stability concern, which is critical for development, but not primarily a security concern in the same vein as exploitable vulnerabilities.
Concept tested: Open-source software security risks
Source: null
Topics
Community Discussion
No community discussion yet for this question.