[Q] ANDROiD 4.4.4 [KK] SecurityPatchLevel 2017-09-05 - Android Q&A, Help & Troubleshooting

hello world
after reading this:
https://source.android.com/security/bulletin/2017-07-01
i am pondering about if it is possible to build a
4.4.4 rom with the SecurityPatchLevel 2017-07-05
although there are many KK devices up and running, no one seems to be able
to build such up-to-date-patchlevel KK rom.
the AOSP bulletin states:
Code:
Source code patches for these issues have been released to the Android Open Source Project (AOSP) repository and linked from this bulletin.
it reads like these patches are available to 4.4.4 also.
if this is correct and these patches are available for 4.4.4
changing to L or M or N is no option and i try to find a way
to create such one!

wow...

maybe the next SPL
there popped up another one: SPL 2017-07-05
maybe now

here we go again...
kinda funny: https://source.android.com/security/bulletin/2017-08-01
Updated AOSP versions: CVE-2017-0713
A-32096780 [2] RCE High 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2

here we go again...
2017-09-05: Complete security patch level string.
This security patch level string indicates that all issues associated with
2017-09-01 and 2017-09-05
(and all previous security patch level strings) are addressed.
hell yea! all is adressed! :fingers-crossed:
CVE References Type Severity Updated AOSP versions
CVE-2017-0752 A-62196835 EoP High 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2
and 4.4.4 is updated! :laugh:
but wait ...

here we go again...
there is a 2017-10-05 even for 4.4.4 ...

left alone with unpatched roms too early!
new year, new luck?!

Related

[Android]need patch OpenSSLX509Certificate

Hi
Does anyone know where to download the patch for version 4.4.4.
patch was descibe here:
https://securityintelligence.com/one-class-to-rule-them-all-new-android-serialization-vulnerability-gives-underprivileged-apps-super-status/#.Vc8VH61tzMq
Google has fixed the two OpenSSLX509Certificate instances by adding the transient modifier to the mContext member. Google has patched Android 5.1 and 5.0 (commit ID de55e62f6c7ecd57d0a91f2b497885c3bdc661d3) and has also backported the patch to Android 4.4 (commit ID b9d6334acde7460502face82417de40e438a3f4). The patch is also available on Android M (build MPZ79M).
Click to expand...
Click to collapse
I can't find it to patch on my pure AOSP

[SamStock ROM][ODEX][DEBLOAT][7.0][920/5 | W8 - F - I ][NOVEMBER PATCH]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Other roms not giving you the performance or battery life you want? Try SAMSTOCK rom. It's so stock that its stock. Some rom makers like to customize their rom by branding it with their name, and I have nothing against that.
This rom however has none of that.​
KNOX WARRANTY VOID: 1 (0X1)​
Features:
-Untouched. Completely stock out of the latest zip from sammobile.
-December Security Patch
-Multi CSC just like stock firmware
-Safetynet Passed
-Private Mode working
-System Status = Official (In DL mode and in about phone)
-Can check for latest updates from samsung
-Play Store > Settings > Device Certification > Certified (MOST ROMS FAIL THIS)
-No branding by me at all
-No changes to any apk
-SE for Android Status: ENFORCING
-Samsung Health working fully
-Latest ROOT by topjohnwu
Whats customized
-this line from build.prop : "ro.config.tima=0"
But why DEV? You said stock.
To make Samsung Health work again.
NO OTHER FILE IN THIS ROM HAS BEEN TOUCHED ABSOLUTE STOCK!!
-Removed Samsung Pass (Does not work on any rom unless official not rooted)
-Removed Samsung Pay (Does not work on any rom custom or stock after knox trip)
Debloated apps include:
All available to reinstall from aroma.
-Facebook
-Instagram
-Onenote
-Peel Smart remote
-Skype
-WhatsApp
-Microsoft Excel
-Microsoft PowerPoint
-Microsoft Word
-Microsoft OneDrive
-Hancom Office
-Samsung Health
-S Voice (Honestly don't torture yourself)
-Yahoo Edge Panels (EDGE ONLY)
Requirements:
-Device SM-G920F/W8/I, SM-G925F/W8/I
-Flash latest firmware from Samsung
-Must be latest Bootloader and modem
-If you come to me with bricked devices I'll honestly just laugh. It says what you need right above this.
Installation:
-Backup your garbage
-Power off
-Charge to 80% or higher
-Boot into TWRP
-Advanced wipe ALL partitions except for /usbstorage
-Install Zip
-Select the garbage you want
-Let it install
-Reboot
FAQS
Q: I see a new update can you update the rom?
A: No those are generally region specific updates. Not major patches. Just carrier fixes. If I did it I would sit here for days.
Q: I checked for and downloaded a new update. I reboots into recovery and then nothing. What happened?
A: You cannot install OTA updates because they require the stock recovery to be installed. TLDR: Ignore the update.
Q: When are you updating this rom?
A: When samsung releases the next MAJOR/MONTHLY security patch update.
Q: When are you adding [Insert feature name here]?
A: Never. Its stock what ever stock comes with is what you get. There are other roms available for that.
Q: My phone is taking too long to boot. What should I do?
A: Did you follow all instructions? First boot takes 10-15 minutes.
Q: Fingerprint reader doesn't work. What do I do?
A: Device needs to be restarted.
Q: Can you remove/debloat [INSERT APP NAME HERE] and put it in aroma?
A: Sure when there's a new patch from Samsung I will.
Q: Does this work with my device?
A: If its a G920F/W8/I OR 925F/W8/I. Yes. Yes it does. If not. Get out.
Q: OK dev my garbage works like you said. Now what?
A: Let me know how you like it. Drop a like and enjoy. :laugh: :good:
Q: Why isn't there just one zip for all devices?
A: Because these aren't custom roms. They are stock. If i did one zip for all devices zip size would be 4GB+
Q: Will this work with my carrier?
A: Please click below to see a full list of supported CSC's.
SM-G920/5W8
-BMC (Bell Mobility)
-BWA (SaskTel)
-ESK (East Link)
-FMC (Fido Mobile)
-GLW (Freedom Mobile)
-KDO (Koodo)
-MTA (Manitoba Telecom)
-RWC (Rogers Wireless)
-TLS (Telus)
-VMC (Virgin Canada)
-VTR (VideoTron)
-XAC (Unlocaked Canada)
SM-G920F
-BTU (United Kingdom)
-CPW (United Kingdom)
-DBT (Germany)
-ITV (Italy)
-KOR (Korea)
-NEE (Finland)
-XEF (France)
-XEO (Poland)
SM-G925F
-BTU (United Kingdom)
-CPW (United Kingdom)
-DBT (Germany)
-ITV (Italy)
-KOR (Korea)
-NEE (Finland)
-XEF (France)
-XEO (Poland)
-XSG (UAE)
SM-920I
-BNG (Bangladesh)
-INS (India)
-INU (India)
-NPL (Nepal)
-SLK (Sri Lanka)
SM-G925I
-BNG (Bangladesh)
-INS (India)
-INU (India)
-NPL (Nepal)
-SLK (Sri Lanka)
Thanks to:
-amarullz for Aroma
-topjohnwu for Magisk 14 Root
-Samsung for the stock rom
-Carriers for doing nothing
DROP THESE GUYS A LIKE TOO THEY DESERVE IT.
For Developers:
-If you want to use this as a base for your rom please PM me and i'll reply asap
-If you want to help add features to aroma them PM me so we can talk business
Samsung Official Security Bulliten:
This is the security patch status. Here you'll be able to see the vulnerabilities that were fixed by Samsung and google.
JULY:
Code:
SMR-JUL-2017
Samsung Mobile is releasing a maintenance release for major flagship models as part of monthly Security Maintenance Release (SMR) process.
This SMR package includes patches from Google and Samsung.
Google patches include patches up to Android Security Bulletin - July 2017 package.
The Bulletin (July 2017) contains the following CVE items:
Critical: CVE-2017-0564, CVE-2016-9794, CVE-2015-7555, CVE-2017-0540, CVE-2017-0673, CVE-2017-0674, CVE-2017-0675, CVE-2017-0676, CVE-2017-0677, CVE-2017-0678, CVE-2017-0679, CVE-2017-0680, CVE-2017-0681, CVE-2017-0469
High: CVE-2017-6423, CVE-2015-9004, CVE-2014-9940, CVE-2017-0648, CVE-2017-6074, CVE-2017-8253, CVE-2017-8273, CVE-2014-9979, CVE-2015-8595, CVE-2017-0664, CVE-2017-0665, CVE-2017-0666, CVE-2017-0667, CVE-2017-0669, CVE-2017-0670, CVE-2017-0671, CVE-2016-2109, CVE-2017-0672, CVE-2017-0684, CVE-2017-0685, CVE-2017-0686, CVE-2017-0688, CVE-2017-0689, CVE-2017-0690, CVE-2017-0691, CVE-2017-0692, CVE-2017-0693, CVE-2017-0694, CVE-2017-0695, CVE-2017-0696, CVE-2017-0697, CVE-2017-0700, CVE-2017-0701, CVE-2017-0702, CVE-2017-0703, CVE-2017-0642
Moderate: CVE-2017-7368, CVE-2017-7364, CVE-2017-8237, CVE-2015-5707, CVE-2016-5863, CVE-2017-8246, CVE-2017-8256, CVE-2017-8257, CVE-2016-3924, CVE-2017-0493, CVE-2015-7995, CVE-2017-3544, CVE-2017-0698, CVE-2017-0699
Low: CVE-2017-8241
※ Please see Android Security Bulletin for detailed information on Google patches.
Along with Google patches, Samsung Mobile provides 16 Samsung Vulnerabilities and Exposures (SVE) items described below, in order to improve our customer's confidence on security of Samsung Mobile devices.
Some of the SVE items may not be included in this package, in case these items were already included in a previous maintenance release.
SVE-2017-8290: Crash via sending broadcast (AdaptiveDisplayColorService)
Severity: Low
Affected versions: KK(4.4), L(5.0/5.1), M(6.0), N(7.x)
Reported on: February 14, 2017
Disclosure status: Privately disclosed.
Lack of appropriate exception handling for Intents including Serializable instance allows attackers crash several system processes resulting in a possible DoS attack.
The patch prevents system crashes by handling unexpected exceptions.
SVE-2017-8888: Buffer overflow in tlc_server
Severity: Medium
Affected versions: M(6.0), N(7.x)
Reported on: April 11, 2017
Disclosure status: Privately disclosed.
There is a potential buffer overflow vulnerability due to not confirming if the size of source data is smaller than the destination buffer.
The patch removes the problematic code.
SVE-2017-8973: Buffer overflow in process_cipher_tdea
Severity: Low
Affected versions: M(6.0), N(7.x)
Reported on: April 11, 2017
Disclosure status: Privately disclosed.
There is a potential buffer overflow vulnerability due to not verifying input and output parameters’ sizes.
The fix avoids a buffer overflow by checking if the size of output data is the same as input data.
SVE-2017-9109: Unintended memory is disclosed in rkp log
Severity: Medium
Affected versions: M(6.0), N(7.x)
Reported on: May 4, 2017
Disclosure status: Privately disclosed.
The vulnerability allows reading data outside of rkp log buffer boundary due to not checking the boundary.
The applied patch avoids an illegal access to memory by checking the boundary.
SVE-2017-9122, SVE-2017-9123, SVE-2017-9124, and SVE-2017-9126: Crash system server via sending broadcast
Severity: Low
Affected versions: N(7.x)
Reported on: May 10, 2017
Disclosure status: Privately disclosed.
Lack of appropriate exception handling for some Intents which cause NullPointerException allows attackers crash a system process resulting in a possible DoS attack.
The patch protects the receiver by changing to protected intent.
Some SVE items included in the Samsung Android Security Update cannot be disclosed at this time.
Acknowledgements
We truely appreciate the following researchers for helping Samsung to improve the security of our products.
- Ryan Johnson and Angelos Stavrou of Kryptowire : SVE-2017-8290, SVE-2017-9122, SVE-2017-9123, SVE-2017-9124, SVE-2017-9126
- Daniel Komaromy : SVE-2017-8888, SVE-2017-8973
- David Berard : SVE-2017-9109
AUGUST:
Code:
SMR-AUG-2017
Samsung Mobile is releasing a maintenance release for major flagship models as part of monthly Security Maintenance Release (SMR) process.
This SMR package includes patches from Google and Samsung.
Google patches include patches up to Android Security Bulletin - August 2017 package.
The Bulletin (August 2017) contains the following CVE items:
Critical: CVE-2017-0714, CVE-2017-0715, CVE-2017-0716, CVE-2017-0718, CVE-2017-0719, CVE-2017-0720, CVE-2017-0721, CVE-2017-0722, CVE-2017-0723, CVE-2017-0745, CVE-2017-0407, CVE-2017-9417
High: CVE-2017-0576, CVE-2016-10286, CVE-2016-10244, CVE-2017-0713, CVE-2017-0724, CVE-2017-0725, CVE-2017-0726, CVE-2017-0727, CVE-2017-0728, CVE-2017-0729, CVE-2017-0730, CVE-2017-0731, CVE-2017-0732, CVE-2017-0733, CVE-2017-0734, CVE-2017-0735, CVE-2017-0736, CVE-2017-0687, CVE-2017-0737
Moderate: CVE-2017-0583, CVE-2016-5346, CVE-2017-6425, CVE-2016-10236, CVE-2017-6426, CVE-2017-7370, CVE-2017-7372, CVE-2017-7373, CVE-2017-0451, CVE-2017-7308, CVE-2017-8264, CVE-2017-8266, CVE-2017-8268, CVE-2017-8258, CVE-2017-0560, CVE-2017-0712, CVE-2017-0738, CVE-2017-0739
Low: CVE-2017-0452
※ Please see Android Security Bulletin for detailed information on Google patches.
Along with Google patches, Samsung Mobile provides 12 Samsung Vulnerabilities and Exposures (SVE) items described below, in order to improve our customer's confidence on security of Samsung Mobile devices.
Some of the SVE items may not be included in this package, in case these items were already included in a previous maintenance release.
SVE-2017-8889, SVE-2017-8891, and SVE-2017-8892: Stack overflow in trustlet
Severity: Low
Affected versions: M(6.0), N(7.x)
Reported on: April 11, 2017
Disclosure status: Privately disclosed.
Lack of boundary checking of a buffer in trustlet can lead to memory corruption.
The applied patch adds boundary checking.
SVE-2017-8890: Over-read in trustlet
Severity: Low
Affected versions: M(6.0), N(7.x)
Reported on: April 11, 2017
Disclosure status: Privately disclosed.
Lack of boundary checking of a buffer in trustlet can lead to unauthorized access to data outside of boundary.
The applied patch adds boundary checking.
SVE-2017-8893: Arbitrary write in trustlet
Severity: Low
Affected versions: M(6.0), N(7.x)
Reported on: April 11, 2017
Disclosure status: Privately disclosed.
Assuming privilege escalation is achieved, lack of boundary checking in a trustlet can lead to arbitrary write.
The applied patch adds boundary checking.
SVE-2017-9008 and SVE-2017-9009: Integer overflow in trustlet
Severity: Low
Affected versions: N(7.x)
Reported on: April 24, 2017
Disclosure status: Privately disclosed.
Lack of boundary checking of a buffer in trustlet can lead to memory corruption.
The patch removed the part of code related to Integer overflow.
SVE-2017-9383: Abnormal screen touch via malformed input with multiwindow_facade API
Severity: Low
Affected versions: M(6.0)
Reported on: May 31, 2017
Disclosure status: Privately disclosed.
Lack of appropriate validation check for display ID can halt system due to NullPointException problem caused by mismatch to a non-existing display.
The supplied patch prevents unexpected exception by confirming the validation of display ID.
Some SVE items included in the Samsung Android Security Update cannot be disclosed at this time.
Acknowledgements
We truely appreciate the following researchers for helping Samsung to improve the security of our products.
- Daniel Komaromy : SVE-2017-8889, SVE-2017-8890, SVE-2017-8891, SVE-2017-8892, SVE-2017-8893, SVE-2017-9008, SVE-2017-9009
- Qing Zhang of Xiaomi and Guangdong Bai of Singapore Institute of Technology (SIT) : SVE-2017-9383
NOVEMBER:
Code:
SMR-NOV-2017
Samsung Mobile is releasing a maintenance release for major flagship models as part of monthly Security Maintenance Release (SMR) process. This Security Update package includes patches from Google and Samsung.
The following CVE items from November 2017 Android Security Bulletin are included in this Security Update package:
Critical
CVE-2017-11053, CVE-2017-9714, CVE-2017-0832, CVE-2017-0833, CVE-2017-0834, CVE-2017-0835, CVE-2017-0836, CVE-2017-0841
High
CVE-2017-9075, CVE-2017-11063, CVE-2017-0830, CVE-2017-0831, CVE-2017-0839, CVE-2017-0840, CVE-2017-0842, CVE-2017-0852, CVE-2017-0853(M 6.x), CVE-2017-0854(M 6.x), CVE-2017-0857(M 6.x), CVE-2017-0858(M 6.x), CVE-2017-0859(M 6.x), CVE-2017-13077, CVE-2017-13078, CVE-2017-13079, CVE-2017-13080, CVE-2017-13081, CVE-2017-13082, CVE-2017-13086, CVE-2017-13087, CVE-2017-13088
Moderate
CVE-2017-0824, CVE-2017-0825, CVE-2017-7187, CVE-2017-9686, CVE-2017-11050, CVE-2017-11067, CVE-2017-11056, CVE-2017-11046, CVE-2017-9706, CVE-2017-11048, CVE-2017-9697, CVE-2017-11051, CVE-2017-9715, CVE-2017-9717, CVE-2017-11054, CVE-2017-11055, CVE-2017-0845, CVE-2017-0847, CVE-2017-0848, CVE-2017-0849, CVE-2017-0850, CVE-2017-0851, CVE-2017-0853(N 7.x, O 8.0), CVE-2017-0854(N 7.x, O 8.0), CVE-2016-2105, CVE-2016-2106, CVE-2017-3731, CVE-2017-0860
Low
None
NSI
CVE-2017-0857(N 7.x, O 8.0), CVE-2017-0858(N 7.x, O 8.0), CVE-2017-0859(N 7.x)
Already included in previous updates
None
Not applicable to Samsung devices
CVE-2017-7374, CVE-2017-0827, CVE-2017-9683, CVE-2017-0826, CVE-2017-0828, CVE-2017-0829, CVE-2017-11062, CVE-2017-9687
※ Please see Android Security Bulletin for detailed information on Google patches.
Along with Google patches, Samsung Mobile provides 6 Samsung Vulnerabilities and Exposures (SVE) items described below, in order to improve our customer's confidence on security of Samsung Mobile devices. Some of the SVE items may not be included in this package, in case these items were already included in a previous maintenance release.
SVE-2017-8973, SVE-2017-8974, SVE-2017-8975: TA Scrypto v1.0 Vulnerability
Severity: Low
Affected versions: M(6,x), N(7.0)
Reported on: April 17, 2017
Disclosure status: Privately disclosed.
A race condition may occur in Secure Driver resulting in potential buffer overflow vulnerability.
The patch prevents race condition and buffer overflow by checking boundary of a buffer.
SVE-2017-10086: Arbitrary file read/write in locked device via mtp
Severity: High
Affected versions: KK(4.4.x), L(5.x), M(6.x), N(7.x)
Reported on: August 17, 2017
Disclosure status: Privately disclosed.
Device responds from malicious MTP command on the locked state.
The patch prevents the device from responding from a malicious MTP command when it receives MTP command on the locked state.
SVE-2017-10465: Bug in MSM8998 chipset’s bootloader that checks integrity of system image (SamFAIL)
Severity: High
Affected versions: N(7.x)
Reported on: October 08, 2017
Disclosure status: Privately disclosed.
A vulnerability in verification logic within the bootloader in Qualcomm MSM8998 chipset allows an attacker to successfully boot the Samsung Galaxy Note8 device with root privilege.
The patch prevents an Attacker from booting Note8 successfully by checking an integrity of system image.
Some SVE items included in the Samsung Android Security Update cannot be disclosed at this time.
Acknowledgements
We truly appreciate the following researchers for helping Samsung to improve the security of our products.
- Salvatore Mesoraca : SVE-2017-10086
- Daniel Komaromy : SVE-2017-8973, SVE-2017-8974, SVE-2017-8975
DECEMBER:
Code:
SMR-DEC-2017
Samsung Mobile is releasing a maintenance release for major flagship models as part of monthly Security Maintenance Release (SMR) process. This Security Update package includes patches from Google and Samsung.
The following CVE items from December 2017 Android Security Bulletin are included in this Security Update package:
Critical
CVE-2017-11013, CVE-2017-11015, CVE-2017-11014, CVE-2017-0427, CVE-2017-0872, CVE-2017-0878, CVE-2017-13151, CVE-2017-13160, CVE-2015-3868, CVE-2017-0675, CVE-2017-6211
High
CVE-2017-0871, CVE-2017-9077, CVE-2017-7541, CVE-2017-0843, CVE-2017-11092, CVE-2017-11028, CVE-2017-0838, CVE-2017-0807, CVE-2017-0870, CVE-2017-13153, CVE-2017-0837, CVE-2017-0873, CVE-2017-0874, CVE-2017-0880, CVE-2017-13148, CVE-2017-13156, CVE-2017-13157, CVE-2017-13158, CVE-2017-13159, CVE-2017-13077, CVE-2017-0879(L5.1, M6.x), CVE-2017-13149(L5.1, M6.x), CVE-2017-13150(M6.x)
Moderate
CVE-2017-11057, CVE-2017-11059, CVE-2017-11061, CVE-2017-11060, CVE-2017-11052, CVE-2017-11064, CVE-2017-0861, CVE-2017-1160, CVE-2017-11073, CVE-2017-11035, CVE-2017-11012, CVE-2017-11085, CVE-2017-11091, CVE-2017-11032, CVE-2017-11024, CVE-2017-11025, CVE-2017-11023, CVE-2017-11029, CVE-2017-11018, CVE-2017-9702, CVE-2017-11089, CVE-2017-8239, CVE-2017-11090, CVE-2017-11093, CVE-2017-8279, CVE-2017-9696, CVE-2017-11058, CVE-2017-11022, CVE-2017-0879(N7.x, O8.0), CVE-2017-13149(N7.x, O8.0), CVE-2017-13150(N7.x, O8.0), CVE-2017-13152
Low
None
NSI
None
Already included in previous updates
None
Not applicable to Samsung devices
CVE-2017-6264, CVE-2017-9690, CVE-2017-11017, CVE-2017-6001, CVE-2017-0862, CVE-2017-0863, CVE-2017-0864, CVE-2017-0865, CVE-2017-0866, CVE-2017-6274, CVE-2017-6275, CVE-2017-11026, CVE-2017-11038, CVE-2017-9719, CVE-2017-9721, CVE-2017-9701, CVE-2017-11027, CVE-2017-0876, CVE-2017-0877
※ Please see Android Security Bulletin for detailed information on Google patches.
Along with Google patches, Samsung Mobile provides 10 Samsung Vulnerabilities and Exposures (SVE) items described below, in order to improve our customer's confidence on security of Samsung Mobile devices. Some of the SVE items may not be included in this package, in case these items were already included in a previous maintenance release.
SVE-2017-8907: Information disclosure on Samsung gpu
Severity: Moderate
Affected versions: M(6.x), N(7.x)
Reported on: April 14, 2017
Disclosure status: Privately disclosed.
kbase_context address in gpu memory node is exposed and it may result in unauthorized information disclosure.
The patch prevents kernel memory address exposure which includes kbase_context address in gpu node.
SVE-2017-10011: muic_set_reg_sel heap_overflow
Severity: Moderate
Affected versions: L(5.1), M(6.x), N(7.x)
Reported on: August 17, 2017
Disclosure status: Privately disclosed.
System can be crashed by non-existence of null pointer check; and buffer overflow vulnerability exists because the size to be copied from user space is not checked.
The patch prevents Null Pointer dereference and buffer overflow when muic register values are read.
SVE-2017-9414: panel_lpm sysfs stackOverflow issue
Severity: Moderate
Affected versions: M(6.x), N(7.x) with Qualcomm chipsets
Reported on: June 5, 2017
Disclosure status: Privately disclosed.
The size of user data is not checked and it makes buffer overflow when user data is copied into an array.
The patch prevents buffer overflow when user data is copied in lpm ctrl debug function.
SVE-2017-10598: Arbitrary Code Execution in the Samsung Bootloader
Severity: Moderate
Affected versions: L(5.x), M(6.x), N(7.x) with Exynos chipsets
Reported on: October 8, 2017
Disclosure status: This issue is publicly known.
S Boot copies ramfs data to its memory without checking validation of the size making it possible to overwrite the code segment of S Boot which can result in arbitrary code execution in bootloader.
The patch prevents arbitrary code execution in bootloader by checking the limit of ramdisk size.
Some SVE items included in the Samsung Android Security Update cannot be disclosed at this time.
Acknowledgements
We truly appreciate the following researchers for helping Samsung to improve the security of our products.
- Yaoguang Chen of Ant-financial Light-Year Security Lab : SVE-2017-8907
- Yu Pan and Yang Dai of Vulpecker Team Qihoo 360 Technology Co. Ltd : SVE-2017-10011, SVE-2017-9414
- Hung Chi Su of Team T5 : SVE-2017-10598
Development Status:
This is the development status section here you will be able to see what I am currently doing for this rom. If I have an older firmware version listed as latest please inform me as I only have worked with W8 devices in the past. Refer to the legend below to see what each status means.
LEGEND
STOPPED: Latest link available. No updates till next patch.
IN DEVELOPMENT: New build uploaded by sammobile. Development begins.
TESTING: Development ended. Ensuring rom is functional.
UPLOADING: Testing has ended now uploading.
BEFORE APPLYING NEW BUILDS. DOWNLOAD NEW STOCK FIRMWARES AND FLASH THEM THROUGH ODIN. THEN FLASH TWRP VIA ODIN THEN MY ROM.​BEFORE APPLYING NEW BUILDS. DOWNLOAD NEW STOCK FIRMWARES AND FLASH THEM THROUGH ODIN. THEN FLASH TWRP VIA ODIN THEN MY ROM.​BEFORE APPLYING NEW BUILDS. DOWNLOAD NEW STOCK FIRMWARES AND FLASH THEM THROUGH ODIN. THEN FLASH TWRP VIA ODIN THEN MY ROM.​
PLEASE BE VERY CAREFUL AS THESE ARE STOCK ROMS THEY ARE NOT CUSTOMIZED SO FLASHING EDGE ROMS ON FLAT MODELS COULD RESULT IN SOFT BRICK, IMEI LOSS OR DEAD EMMC. YOU HAVE BEEN WARNED. IF YOU CLICK THE DOWNLOAD BUTTON YOU AGREE THAT YOU TAKE FULL RESPONSIBILITY FOR ANY DAMAGES YOU MAY CAUSE. IF YOU BLAME ME OR ANY OTHER DEVELOPERS FOR YOUR FAILURE TO UNDERSTAND THESE MESSAGES THEN WE WILL NOT HELP YOU SOLVE YOUR PROBLEM.​
GALAXY S6
920W8 STATUS: STOPPED
BUILD NUMBER: G920W8VLS5DQK1
Security LEVEL: 2017-11-01
REASON: Waiting for December patch from Samsung. Nov. Patch Available.
NEXT UPDATE ETA: December (Date Unknown)
LINK: DOWNLOAD
920F STATUS: STOPPED
BUILD NUMBER: G920FXXS5EQL1
Security LEVEL: 2017-12-01
REASON: December patch Finished. Link Available.
NEXT UPDATE ETA: January (Date Unknown)
LINK: DOWNLOAD
920I STATUS: STOPPED
BUILD NUMBER: G920IDVS3FQL5
Security LEVEL: 2017-12-01
REASON: December patch Finished. Link Available.
NEXT UPDATE ETA: January (Date Unknown)
LINK: DOWNLOAD
GALAXY S6 EDGE
925W8 STATUS: STOPPED
BUILD NUMBER: G925W8VLS5DQH1
Security LEVEL: 2017-08-01
REASON: Waiting for December patch from Samsung. Aug. Patch Available.
NEXT UPDATE ETA: September (Date Unknown)
LINK: DOWNLOAD
925F STATUS: STOPPED
BUILD NUMBER: G925FXXS5EQL1
Security LEVEL: 2017-12-01
REASON: December patch Finished. Link Available.
NEXT UPDATE ETA: January (Date Unknown)
LINK: DOWNLOAD
925I STATUS: STOPPED
BUILD NUMBER: G925IDVS3FQL5
Security LEVEL: 2017-12-01
REASON: December patch Finished. Link Available.
NEXT UPDATE ETA: January (Date Unknown)
LINK: DOWNLOAD
Bugs:
-Samsung Internet Secret Mode works initially then never again.
TEMP FIX: Use internet beta from play store. (Basically same app but allows p0rn mode to work.)
XDA:DevDB Information
SamStock ROM, ROM for the Samsung Galaxy S6
Contributors
Moiz Ahmed
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest Modem and Bootloader
Based On: Samsung Stock
Version Information
Status: Stable
Stable Release Date: 2017-07-31
Created 2017-08-01
Last Updated 2017-12-25
Reserved
DECEMBER BRANCH STARTED​
Devices updated:
S6 FLAT
-920I
-920F
S6 EDGE
-925F
-925I
Devices not yet updated:
S6 FLAT
-920W8 (NOV)
S6 EDGE
-925W8 (AUG)
FIXES:
-Removed SVCAgent from rom to aroma. (PART OF S-Voice)
-root updated to magisk 14
-Added DTM CSC for 920F
-other fixes include bug fixes in samsung source code found in the SMR and during installation.
Reserved
Moiz Ahmed said:
Other roms not giving you the performance or battery life you want? Try SAMSTOCK rom. It's so stock that its stock. Some rom makers like to customize their rom by branding it with their name, and I have nothing against that.
This rom however has none of that.​
Features:
-Untouched. Completely stock out of the latest zip from sammobile.
-July Security Patch
-Multi CSC just like stock firmware
-Safetynet Passed
-Private Mode working
-System Status = Official (In DL mode and in about phone)
-Can check for and DL latest updates from samsung
-No branding by me at all
-No changes to any apk
-SE for Android Status: ENFORCING
-Samsung Health working fully
-Latest ROOT by topjohnwu
Whats customized
-this line from build.prop : "ro.config.tima=0"
But why DEV? You said stock.
To make Samsung Health work again.
NO OTHER FILE IN THIS ROM HAS BEEN TOUCHED ABSOLUTE STOCK!!
Debloated apps include:
All available to reinstall from aroma.
-Facebook
-Instagram
-Onenote
-Peel Smart remote
-Skype
-WhatsApp
-Microsoft Excel
-Microsoft PowerPoint
-Microsoft Word
-Microsoft OneDrive
-Hancom Office
-Samsung Health
-S Voice (Honestly don't torture yourself)
-Yahoo Edge Panels (EDGE ONLY)
Requirements:
-Device SM-G920W8, SM-G925W8
-Flash latest firmware from Samsung
-Must be latest Bootloader and modem
-If you come to me with bricked devices I'll honestly just laugh. It says what you need right above this.
Installation:
-Backup your garbage
-Power off
-Charge to 80% or higher
-Boot into TWRP
-Advanced wipe all partitions except for /usbstorage
-Install Zip
-Select the garbage you want
-Let it install
-Reboot
FAQS
Q: When are you updating this rom?
A: When samsung releases the next update
Q: When are you adding [Insert feature name here]?
A: Never. Its stock what ever stock comes with is what you get. There are other roms available for that.
Q: My phone is taking too long to boot. What should I do?
A: Did you follow all instructions? First boot take 10-15 minutes.
Q: Fingerprint reader doesn't work. What do I do?
A: Device needs to be restarted.
Q: Can you remove/debloat [INSERT APP NAME HERE] and put it in aroma?
A: Sure when there's a new patch from Samsung I will.
Q: Does this work with my device?
A: If its a G920W8/925W8. Yes. Yes it does. If not. Get out.
Q: OK dev my garbage works like you said. Now what?
A: Let me know how you like it. Drop a like and enjoy. :laugh: :good:
Thanks to:
-amarullz for Aroma
-topjohnwu for Magisk 13.3 Root
-Samsung for the stock rom
-Carriers for doing nothing
DROP THESE GUYS A LIKE TOO THEY DESERVE IT.
For Developers:
-If you want to use this as a base for your rom please PM me and i'll reply asap
-If you want to help add features to aroma them PM me so we can talk business
Development Status:
This is the development status section here you will be able to see what I am currently doing for this rom.
920W8 STATUS: STOPPED
BUILD NUMBER: G920W8VLS5DQG1
REASON: Rev 1.2 Uploaded. No new updates from samsung.
ETA: August (Day Unknown)
920F STATUS: IN DEVELOPMENT
REASON: Working on initial release. 920F Testers needed.
ETA: Unknown
925W8 STATUS: STOPPED
BUILD NUMBER: G925W8VLS5DQG1
REASON: Uploaded. No new updates from samsung.
ETA: August (Day Unknown)
925F STATUS: IN DEVELOPMENT
REASON: Working on initial release. 925F Testers needed.
ETA: Unknown
Bugs:
-Samsung Internet Secret Mode works initially then never again.
TEMP FIX: Use internet beta from play store. (Basically same app but allows secret mode to work.)
Download:
PLEASE BE PATIENT AS I TRANSFER FILES TO A NEW DRIVE ACCOUNT. LINKS WILL BE UP SOON.
SM-G920W8NOT AVAILABLE
SM-G925W8NOT AVAILABLE
SM-G920F NOT AVAILABLE
SM-G925F NOT AVAILABLE
XDA:DevDB Information
SamStock ROM, ROM for the Samsung Galaxy S6
Contributors
Moiz Ahmed
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest Modem and Bootloader
Based On: Samsung Stock
Version Information
Status: Stable
Stable Release Date: 2017-07-31
Created 2017-08-01
Last Updated 2017-07-31
Click to expand...
Click to collapse
What about SM-G925I?
nokia_16 said:
What about SM-G925I?
Click to expand...
Click to collapse
If a lot more people want it i'll do a 925I and 920I. I have a Ryzen 5 CPU and extraction and compression of these firmwares simultaneously doesn't take too much time but i need people to actually use it otherwise my work is worth nothing.
Hi,
Thanks for uploading the Rom. I'd like to have a look. Though two questions :
A) the description about support for g920f is a bit inconsistent. It says it is stopped and you say only the g920w variants work, but then there is a download link.
B) which csc is this based on? Does VoLTE work? Especially on German t-mobile? It usually requires a DTM csc
Br
Johannes
orgler said:
Hi,
Thanks for uploading the Rom. I'd like to have a look. Though two questions :
A) the description about support for g920f is a bit inconsistent. It says it is stopped and you say only the g920w variants work, but then there is a download link.
B) which csc is this based on? Does VoLTE work? Especially on German t-mobile? It usually requires a DTM csc
Br
Johannes
Click to expand...
Click to collapse
Hi sorry for the confusion. Stopped means i'm not doing any work on it anymore till next samsung update. As for csc when I unpacked the stock zip there was only one csc which led me to believe its an unlocked csc. All other models had multi csc support. Try it and let me know please i only have the W8 model. I'll take a look tomorrow morning.
Moiz Ahmed said:
If a lot more people want it i'll do a 925I and 920I. I have a Ryzen 5 CPU and extraction and compression of these firmwares simultaneously doesn't take too much time but i need people to actually use it otherwise my work is worth nothing.
Click to expand...
Click to collapse
May be once you do for 925I a lot user may opt to your rom coz there is no stock debloated nought rom for G925I. Hence its my request to make your rom for G925I. This is only an request. Also if you decided to do so go for INS csc or multi csc whch has INS or INU, coz both csc volte will work.
nokia_16 said:
May be once you do for 925I a lot user may opt to your rom coz there is no stock debloated nought rom for G925I. Hence its my request to make your rom for G925I. This is only an request. Also if you decided to do so go for INS csc or multi csc whch has INS or INU, coz both csc volte will work.
Click to expand...
Click to collapse
Ok I think I'll start tomorrow morning. Please link me to the latest multi csc for 920I and 925I from sammobile.com
Moiz Ahmed said:
Ok I think I'll start tomorrow morning. Please link me to the latest multi csc for 920I and 925I from sammobile.com
Click to expand...
Click to collapse
Sammobile has not yet updated latest version for g925i ..I am sending you direct link for g925i. Updated one similar to sammobile.
Here is the link...
nokia_16 said:
Sammobile has not yet updated latest version for g925i ..I am sending you direct link for g925i. Updated one similar to sammobile.
Here is the link...
Click to expand...
Click to collapse
Great downloading now. Could you also send me the 920I link usually same last 4 characters as 925I.
nokia_16 said:
Sammobile has not yet updated latest version for g925i ..I am sending you direct link for g925i. Updated one similar to sammobile.
Here is the link...
Click to expand...
Click to collapse
Great downloading now. Could you send me the 920I link. It's usually same last 4 build number characters.
Can anyone point me in the direction where I can find the latest modem and bootloader for my SM-G920F? And does the region of the modem matter? tnx
amgat said:
Can anyone point me in the direction where I can find the latest modem and bootloader for my SM-G920F? And does the region of the modem matter? tnx
Click to expand...
Click to collapse
Hi yes region does matter. the simple way would be to go HERE download the latest firmware for your model and region then flash using odin. then return here and flash this. TO find out your region go to dialer type *#1234# and the values that appear will guide you in finding your region.
Thank you Moiz Ahmed!. Does the firmware contain the latest modem as well? Or is not that important to update the modem?
amgat said:
Thank you Moiz Ahmed!. Does the firmware contain the latest modem as well? Or is not that important to update the modem?
Click to expand...
Click to collapse
Very important to update both modem and bootloader. Best to do a complete wipe flash latest stock then this.
The firmware file is 1.8GB in size. So the firmware file from updato is actually the stock ROM right? Sorry for asking dumb questions
Does Secure Folder work with this rom?
amgat said:
The firmware file is 1.8GB in size. So the firmware file from updato is actually the stock ROM right? Sorry for asking dumb questions
Click to expand...
Click to collapse
Yes it is.
huyhung411991 said:
Does Secure Folder work with this rom?
Click to expand...
Click to collapse
Nope

OOS H2OS 3.1.4 March 2018 security patch update - for developers.

Can some developer add the patches to the stock rom to get it updated in terms of security?

[ROM][SM-G850W][sltecan] LineageOS 16.0 UNOFFICIAL for the Galaxy Alpha (S801)

LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
This is an unofficial LineageOS 16.0 build for the SM-G850W which is a Snapdragon variant of Galaxy Alpha and has an unlocked bootloader.
This ROM does not work with Exynos variant (SM-G850F) nor a locked bootloader (SM-G850A).
Known Issues
None
Instructions
Make sure that your SM-G850W has the Lollipop bootloader and modem (The last installed stock ROM must be 5.0.2).
Flash TWRP recovery via Odin.
Use Odin without 'Auto Reboot' option.
After flashing TWRP via Odin, reboot to TWRP recovery (Vol UP + Home + Power). Don't reboot to the stock image which restores the stock recovery.
Boot to TWRP recovery (Vol UP + Home + Power).
Optional: Wipe data / Factory Reset
Install the ROM (Lineage zip).
Optional: Install Magisk to get root.
Install the Google Apps (Open GApps 9.0).
Enjoy!
Downloads
All: https://www.androidfilehost.com/?w=files&flid=42013
LineageOS 16.0: lineage-16.0-20191212-UNOFFICIAL-sltecan.zip
TWRP: twrp-3.3.1-1-sltecan.tar
Recommended Bootloader/Modem: G850WVLU1BPG1_G850WVLU1BPG1_bootmodem.tar
Sources
https://github.com/kyasu/android_kernel_samsung_msm8974
https://github.com/kyasu/android_device_samsung_sltecan
https://github.com/kyasu/android_vendor_samsung_sltecan
XDA:DevDB Information
[ROM][SM-G850W][sltecan] LineageOS 16.0 UNOFFICIAL for the Galaxy Alpha (S801), ROM for the Samsung Galaxy Alpha
Contributors
kyasu, LineageOS Devs
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Stable
Created 2018-09-30
Last Updated 2019-12-12
Reserved
Thx, downloading.
What about g850f
lineage-16.0-20181012-UNOFFICIAL-sltecan.zip
New build is available (See the first post).
Sync with the latest LineageOS source (October 2018 Security Patch).
Now NFC works.
Changes:
https://github.com/kyasu/android_device_samsung_sltecan/commits/lineage-16.0
https://github.com/kyasu/android_kernel_samsung_msm8974/commits/lineage-16.0
Very sad is bagging about g-850f in same time when for Snapdragon variant rom is went to Android 9.0 (Pie).
Look as discrimination of Exynos.
Very sad story.
lineage-16.0-20181020-UNOFFICIAL-sltecan.zip
New build is available (See the first post).
Sync with the latest LineageOS source.
Use Snap camera.
Changes:
https://github.com/kyasu/android_device_samsung_sltecan/commits/lineage-16.0
https://github.com/kyasu/android_kernel_samsung_msm8974/commits/lineage-16.0
Any chance this could get released to SM-G850F?
lineage-16.0-20181115-UNOFFICIAL-sltecan.zip
New build is available (See the first post).
Sync with the latest LineageOS source (November 2018 Security Patch).
Changes:
https://github.com/kyasu/android_device_samsung_sltecan/commits/lineage-16.0
https://github.com/kyasu/android_kernel_samsung_msm8974/commits/lineage-16.0
lineage-16.0-20181209-UNOFFICIAL-sltecan.zip
New build is available (See the first post).
Sync with the latest LineageOS source (December 2018 Security Patch).
Changes:
https://github.com/kyasu/android_device_samsung_sltecan/commits/lineage-16.0
https://github.com/kyasu/android_kernel_samsung_msm8974/commits/lineage-16.0
Typo:
LineageOS 15.1: lineage-16.0-20181209-UNOFFICIAL-sltecan.zip
should say
LineageOS 16.0: xxx
ty for the ROM and ty for keeping the alpha alive.
vasilli81 said:
Typo:
LineageOS 15.1: lineage-16.0-20181209-UNOFFICIAL-sltecan.zip
should say
LineageOS 16.0: xxx
ty for the ROM and ty for keeping the alpha alive.
Click to expand...
Click to collapse
Typo fixed. Thanks.
lineage-16.0-20190112-UNOFFICIAL-sltecan.zip
New build is available (See the first post).
Sync with the latest LineageOS source (January 2019 Security Patch).
Changes:
https://github.com/kyasu/android_device_samsung_sltecan/commits/lineage-16.0
https://github.com/kyasu/android_kernel_samsung_msm8974/commits/lineage-16.0
lineage-16.0-20190210-UNOFFICIAL-sltecan.zip
New build is available (See the first post).
Sync with the latest LineageOS source (February 2019 Security Patch).
Changes:
https://github.com/kyasu/android_device_samsung_sltecan/commits/lineage-16.0
https://github.com/kyasu/android_kernel_samsung_msm8974/commits/lineage-16.0
lineage-16.0-20190309-UNOFFICIAL-sltecan.zip
New build is available (See the first post).
Sync with the latest LineageOS source (March 2019 Security Patch).
Changes:
https://github.com/kyasu/android_device_samsung_sltecan/commits/lineage-16.0
https://github.com/kyasu/android_kernel_samsung_msm8974/commits/lineage-16.0
Hi,
First of all, thank you for the great job. I use it since Marshmallow version and it's always perfect. I have only could of issues:
1. Cannot setup the fingerprint (it was always here, I've never succeed with this)
2. When the device is completely charged and I disconnect the cable, it starts play the Notification sound and the only way to stop it is reboot. I have this problem only with the last version. How can I fix it?
lineage-16.0-20190408-UNOFFICIAL-sltecan.zip
New build is available (See the first post).
Sync with the latest LineageOS source (April 2019 Security Patch).
Changes:
https://github.com/kyasu/android_device_samsung_sltecan/commits/lineage-16.0
https://github.com/kyasu/android_kernel_samsung_msm8974/commits/lineage-16.0
lineage-16.0-20190511-UNOFFICIAL-sltecan.zip
New build is available (See the first post).
Sync with the latest LineageOS source (May 2019 Security Patch).
TWRP 3.3.0 is available (See the first post).
Changes:
https://github.com/kyasu/android_device_samsung_sltecan/commits/lineage-16.0
https://github.com/kyasu/android_kernel_samsung_msm8974/commits/lineage-16.0
lineage-16.0-20190609-UNOFFICIAL-sltecan.zip
New build is available (See the first post).
Sync with the latest LineageOS source (June 2019 Security Patch).
TWRP 3.3.1 is available (See the first post).
Changes:
https://github.com/kyasu/android_device_samsung_sltecan/commits/lineage-16.0
https://github.com/kyasu/android_kernel_samsung_msm8974/commits/lineage-16.0
zartell said:
Very sad is bagging about g-850f in same time when for Snapdragon variant rom is went to Android 9.0 (Pie).
Look as discrimination of Exynos.
Very sad story.
Click to expand...
Click to collapse
Never worked on roms before, but I hear that working on Exynos and/or kirin can be a pain due to some sources not being available. for example lineage OS 14.1 by modpunk got some camera issues and no fingerprint sensor. Note 3 Neo(Exynos) nougat roms got issues with incall audio. Issues like these are usually due to drivers not being open source (or being too old). So unless you work hard on it, you will just end up with a half functioning device.

Where would you start if you are trying to build android 13 for msm8916/8939?

since android 12, lineageos source doesn't support 8916, even the folders like hardware/qcom-caf/msm8916 are missing... you have to patch the source, just having device tree/kernel/vendor is not enough. i know that it's possible, @daviiid99 made android 13 for j5 with the helps of @Ivan_Meler and @html6405 https://forum.xda-developers.com/t/...0-x-for-galaxy-j5-unified-2022-09-28.4493121/
i'm trying to build for asus Z00T and Z00L if possible. Z00T has 8939, Z00L has 8939 and 8916 variants.
since it's been done before, trying to figure everything out by myself doesn't make any sense and its above my knowledge level rn. even daviiid99 got some help.
i have the working device sources for android11, R roms are fully functional without any major issues. how can i patch the android source for msm8916 support and adapt R sources for T?

Categories

Resources