Hermes Framework Version Metadata Inconsistency #49872
Labels
Needs: Author Feedback
Needs: Repro
This issue could be improved with a clear list of steps to reproduce the issue.
Hermes Framework Version Metadata Inconsistency
Summary
The Hermes framework's version metadata (Info.plist and binary version) doesn't reflect the actual codebase version when built, causing issues with security scanning tools. The version numbers defined in build files (0.12.0) don't match the actual codebase version (0.13.0).
Discovery Context
This issue was identified during a security audit of a React Native mobile application. Looking at Snyk's vulnerability database for Hermes, we can see multiple vulnerabilities that are version-dependent, making accurate version reporting crucial for security assessment.
Investigation Steps Taken
Initial Observation:
Local Version Verification:
Binary Version Check:
otool -L ios/Pods/hermes-engine/destroot/Library/Frameworks/universal/hermes.xcframework/ios-arm64/hermes.framework/hermes # Output showed: @rpath/hermes.framework/hermes (compatibility version 0.12.0, current version 0.12.0)
Version numbers are defined in multiple Hermes build files:
Impact
The issue creates unnecessary overhead across security, development, and compliance processes, requiring manual intervention for what should be an automated verification process.
Environment
The text was updated successfully, but these errors were encountered: