Periscope app being used for child grooming


CHILDREN as young as NINE are being groomed by paedophiles on the live-streaming app Periscope, it has emerged.

Perverts are using it to watch youngsters’ broadcasts and bombard them with requests to remove their clothes or make explicit videos.

The grooming was revealed by the BBC, which then handed the evidence to police.

Periscope, which has more than 10 million users, allows people to film themselves on their smartphones and broadcast this live to anyone in the world.

In recent years it has been criticised for its users’ ability to globally broadcast live sport which would normally require viewers to pay subscription fees.

The BBC investigation found people sending messages to children as young as nine that included requests for them to “show skirt under desk” or “take off your top”.

Others sent pervy messages such as “ever had sex?”, “what’s your cup size sexy?” and “can I send you money for a show?”

Claire Lilley, head of online child safety at the NSPCC, called the investigation’s findings “disturbing”.

To see someone “so clearly groomed for sexual purposes by a pack of people online” was “shocking”, she added.

A spokesperson for Pericope’s owner, Twitter, stated: “We have a strong content moderation policy and encourage viewers to report comments they feel are abusive.

“We have zero tolerance for any form of child sexual exploitation.”

Earlier this year a teenage girl was jailed for live-streaming a video of her friend being raped via the Periscope app.

Marina Lonina, 19, was sentenced in Columbus, Ohio, on Monday after pleading guilty to obstructing justice under a deal with prosecutors.

Story by The Sun

CCRA begins next step in the right direction

Last nights Board of Directors meeting went extremely well; appropriately structuring the Board, electing new positions and revising certain bylaws. At the time our President and Executive Director Matthew Baumgartner had a difficult decision to make between staying on the Board voluntarily or taking the Executive Director/CEO position full time paid. 

Before President Baumgartner’s resignation of his Board seat, he decided to nominate Vice President Stephen Bernardoni for the Presidential Chair. Mr. Bernardoni accepted the nomination running unopposed and was officially voted in by the board unanimously.

Legacy President Mr. Baumgartner made a speech during his resignation and had this to say;

“It has been my honor to serve this Agency as its President/Founder and Executive Director for seven great years! As we continue to grow there will be decisions that will need to be made and this is one of them. 

I feel it would be in the best interest of the Agency if I’m able to dedicate full-time to our operations as the CEO. In order for CCRA to exceed on the cusp of our success, it is imperative that my voice is still heard as a non-voting member of the board and to maintain a healthy partnership between the Office of the Director and Office of the President. 

My decision is not that I’d be stepping down, but of that to excel forward as I continue to mentor, guide and teach those coming into the Agency both on the board and in operations. Again, thank you for this opportunity and working so hard as a dedicated team. Together, we’ll stand against cyber crime world-wide!”

CCRA partners with Stand for the Silent


CCRA and Stand for the Silent held a partnership meeting last Thursday, to discuss how the two organizations could assist each other for October’s Cyber Bullying Awareness Month. Both organizations agreed that this partnership was an exciting movement for each other.

CCRA administration stated that the main reason for their respect in this partnership was due to additional resources now available. “We now have a place to refer victims to, where they can talk about their issues, such as bullying and depression” said Stephen Bernardoni, Vice Executive. “Mr. Smalley was also happy that his organization now has resources for those who need assistance with finding hidden suspects involved in their situation.”

As the partnership progresses, both organizations will promote one another in October and attempt to spread awareness about one another’s services and abilities.

Critical Patches Issued for Microsoft Products, 07-11-2017

MS-ISAC ADVISORY NUMBER:
2017-063

DATE ISSUED:
07/11/2017

SUBJECT:
Critical Patches Issued for Microsoft Products, July 11, 2017

OVERVIEW:
Multiple vulnerabilities have been discovered in Microsoft products, the most severe of which could allow for remote code execution. Successful exploitation of the most severe of these vulnerabilities could result in an attacker gaining the same privileges as the logged on user. Depending on the privileges associated with the user, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

THREAT INTELLIGENCE:
There are currently no reports of these vulnerabilities being exploited in the wild.

SYSTEMS AFFECTED:
• Microsoft Internet Explorer 9, 10, 11
• Microsoft Edge
• Microsoft .NET Framework
• Microsoft Windows: 7, 8.1, RT 8.1, 10
• Microsoft Windows Server: 2008, 2008 R2, 2012, 2012 R2, 2016
• Microsoft Windows Server Core Installations: 2008, 2008 R2, 2012, 2012 R2, 2016
• Microsoft Office Web Apps 2010
• Microsoft Office 2007, 2010, 2011, 2013, 2016
• Microsoft SharePoint Enterprise Server 2013, 2016

RISK:
Government:
• Large and medium government entities: High
• Small government entities: Medium
Businesses:
• Large and medium business entities: High
• Small business entities: Medium
Home users: Low

TECHNICAL SUMMARY:
Microsoft products are prone to multiple vulnerabilities, the most severe of which could allow for remote code execution.

A full list of all vulnerabilities can be found at the link below.
https://portal.msrc.microsoft.com/en-us/security-guidance

Successful exploitation of the most severe of these vulnerabilities could result in an attacker gaining the same privileges as the logged on user. Depending on the privileges associated with the user, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

RECOMMENDATIONS:
We recommend the following actions be taken:
• Apply appropriate patches or appropriate mitigations provided by Microsoft to vulnerable systems immediately after appropriate testing.
• Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack.
• Remind users not to visit un-trusted websites or follow links provided by unknown or un-trusted sources.
• Inform and educate users regarding threats posed by hypertext links contained in emails or attachments especially from un-trusted sources.
• Apply the Principle of Least Privilege to all systems and services.

REFERENCES:
Microsoft:
https://portal.msrc.microsoft.com/en-us/security-guidance
https://portal.msrc.microsoft.com/en-us/security-guidance/releasenotedetail/f2b16606-4945-e711-80dc-000d3a32fc99

CCRA prepares to kick off #standing4them campaign

standing4themlogo

CCRA’s campaign for Cyber Bullying Awareness Month in October will be #standing4them. This campaign is intended to reach not only the online community, but the world as a whole in taking a stand with the current and past victims of online bullying. Many states, including Texas, have already made it against the law to cyberbully and cyberstalk others.

There are many ways that anyone can help in this campaign! Simply spreading the word, that cyber bullying is a huge problem in our society is the first step. Second, stand up for those you see victimized online! If you don’t feel like getting involved, let someone know, such as a police officer, teacher, preacher, or friend. Finally, donating to organizations that provide education is a tremendous help. Never be afraid to speak your story and mind.

October 1, 2017 will be day one of our anti bullying campaign. We of course always encourage the stand against bullying of all forms, no matter the location or time.

Contact us today to find other ways to get involved!

Multiple Vulnerabilities in Google Android

img_1344

 

DATE ISSUED:
07/07/2017

SUBJECT:
Multiple Vulnerabilities in Google Android OS Could Allow for Arbitrary Code Execution

OVERVIEW:
Multiple vulnerabilities have been discovered in the Google Android operating system (OS), the most severe of which could allow for arbitrary code execution. Android is an operating system developed by Google for mobile devices, including, but not limited to, smartphones, tablets, and watches. These vulnerabilities could be exploited through multiple methods such as email, web browsing, and MMS when processing media files. Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution in the context of the application. Depending on the privileges associated with this application, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. If this application has been configured to have fewer user rights on the system, exploitation of the most severe of these vulnerabilities could have less impact than if it was configured with administrative rights.

THREAT INTELLIGENCE:
There are currently no reports of these vulnerabilities being exploited in the wild.

SYSTEMS AFFECTED:
• Android OS builds utilizing Security Patch Levels prior to July 5, 2017

RISK:
Government:
• Large and medium government entities: High
• Small government entities: High
Businesses:
• Large and medium business entities: High
• Small business entities: High
Home users: High

TECHNICAL SUMMARY:
Google Android OS is prone to multiple vulnerabilities, the most severe of which could allow for arbitrary code execution. Details of these vulnerabilities are as follows:

• An arbitrary code execution vulnerability in Runtime. (CVE-2017-3544)
• Multiple arbitrary code execution vulnerabilities in Framework. (CVE-2017-0664, CVE-2017-0665, CVE-2017-0666, CVE-2017-0667, CVE-2017-0668, CVE-2017-0669, CVE-2017-0670)
• Multiple arbitrary code execution vulnerabilities in Libraries. (CVE-2017-0671, CVE-2016-2109, CVE-2017-0672)
• Multiple arbitrary code execution vulnerabilities in Media Framework. (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-0682, CVE-2017-0683, 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-0698, CVE-2017-0699)
• Multiple arbitrary code execution vulnerabilities in System UI. (CVE-2017-0700, CVE-2017-0701, CVE-2017-0702, CVE-2017-0703, CVE-2017-0704)
• Multiple arbitrary code execution vulnerabilities in Broadcom Components. (CVE-2017-9417, CVE-2017-0705, CVE-2017-0706)
• Multiple arbitrary code execution vulnerabilities in HTC Components. (CVE-2017-0707, CVE-2017-0708, CVE-2017-0709)
• Multiple Arbitrary code execution in Kernel Components. (CVE-2017-6074, CVE-2017-5970, CVE-2015-5707, CVE-2017-0710, CVE-2017-7308, CVE-2014-9731)
• An arbitrary code execution vulnerability in MediaTek Components. (CVE-2017-0711)
• Multiple arbitrary code execution vulnerabilities in NVIDIA Components. (CVE-2017-0340, CVE-2017-0326)
• Multiple arbitrary code execution vulnerabilities in Qualcomm Components. (CVE-2017-8255, CVE-2016-10389, CVE-2017-8253, CVE-2017-8262, CVE-2017-8263, CVE-2017-8267, CVE-2017-8273, CVE-2016-5863, CVE-2017-8243, CVE-2017-8246, CVE-2017-8256, CVE-2017-8257, CVE-2017-8259, CVE-2017-8260 CVE-2017-8261, CVE-2017-8264, CVE-2017-8265, CVE-2017-8266, CVE-2017-8268, CVE-2017-8270, CVE-2017-8271, CVE-2017-8272, CVE-2017-8254, CVE-2017-8258, CVE-2017-8269)
• Multiple arbitrary code execution vulnerabilities in Qualcomm Closed-Source Components. (CVE-2014-9411, CVE-2014-9968, CVE-2014-9973, CVE-2014-9974, CVE-2014-9975, CVE-2014-9977, CVE-2014-9978, CVE-2014-9979, CVE-2014-9980, CVE-2015-0575, CVE-2015-8592, CVE-2015-8595, CVE-2015-8596, CVE-2015-9034, CVE-2015-9035, CVE-2015-9036, CVE-2015-9037, CVE-2015-9038, CVE-2015-9039, CVE-2015-9040, CVE-2015-9041, CVE-2015-9042, CVE-2015-9043, CVE-2015-9044, CVE-2015-9045, CVE-2015-9046, CVE-2015-9047, CVE-2015-9048, CVE-2015-9049, CVE-2015-9050, CVE-2015-9051, CVE-2015-9052, CVE-2015-9053, CVE-2015-9054, CVE-2015-9055, CVE-2015-9060, CVE-2015-9061, CVE-2015-9062, CVE-2015-9067, CVE-2015-9068, CVE-2015-9069, CVE-2015-9070, CVE-2015-9071, CVE-2015-9072, CVE-2015-9073, CVE-2016-10343, CVE-2016-10344, CVE-2016-10346, CVE-2016-10347, CVE-2016-10382, CVE-2016-10383, CVE-2016-10388, CVE-2016-10391, CVE-2016-5871, CVE-2016-5872)

Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution in the context of the application. Depending on the privileges associated with this application, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. If this application has been configured to have fewer user rights on the system, exploitation of the most severe of these vulnerabilities could have less impact than if it was configured with administrative rights.

RECOMMENDATIONS:
We recommend the following actions be taken:
• Apply appropriate updates provided by Google Android or mobile carriers to vulnerable systems, immediately after appropriate testing.
• Remind users to download apps only from trusted vendors in the Play Store.
• Remind users not to visit un-trusted websites or follow links provided by unknown or un-trusted sources.
• Inform and educate users regarding the threats posed by hypertext links contained in emails or attachments especially from un-trusted sources.

REFERENCES:
Android:
https://source.android.com/security/bulletin/2017-07-01

CVE:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-9411
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-9731
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-9968
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-9973
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-9974
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-9975
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-9977
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-9978
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-9979
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-9980
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0575
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5707
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-8592
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-8595
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-8596
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9034
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9035
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9036
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9037
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9038
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9039
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9040
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9041
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9042
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9043
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9044
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9045
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9046
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9047
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9048
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9049
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9050
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9051
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9052
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9053
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9054
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9055
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9060
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9061
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9062
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9067
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9068
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9069
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9070
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9071
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9072
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9073
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2109
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5863
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5871
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5872
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10343
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10344
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10346
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10347
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10382
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10383
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10388
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10389
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10391
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0340
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0326
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0540
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0673
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0674
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0675
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0676
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0677
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0678
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0679
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0680
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0681
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0682
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0683
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0684
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0685
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0686
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0688
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0689
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0690
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0691
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0692
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0693
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0694
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0695
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0696
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0697
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0698
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0699
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0664
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0665
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0666
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0667
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0668
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0669
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0670
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0671
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0672
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0700
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0701
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0702
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0703
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0704
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0705
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0706
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0707
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0708
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0709
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0710
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0711
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3544
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5970
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-6074
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7308
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8255
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8253
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8262
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8263
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8267
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8273
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8243
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8246
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8256
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8257
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8259
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8260
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8261
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8264
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8265
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8266
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8268
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8270
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8271
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8272
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8254
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8258
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8269
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9417

24×7 Security Operations Center
Multi-State Information Sharing and Analysis Center (MS-ISAC)
31 Tech Valley Drive
East Greenbush, NY 12061
SOC@cisecurity.org – 1-866-787-4722

LaVergne detectives warn parents about signs of online predators

8e283468-42fc-425e-a5d3-0e9596ac3bf5-large16x9_cellmap

LAVERGNE, Tenn. — Detectives in LaVergne asked parents Friday to watch out for ways predators might try to lure in children and teenagers.

Sgt David Durham with the LaVergne Police Department said he’s seen the way predators work to contact kids and teens.

“A lot of times you will see somebody taking a kid’s photo off the internet and using that as their profile so they can use that to get in good with the kids and say they go to that school,” Durham said. “They will use a persona to get the kids to trust. Then that’s when the conversation starts, and it progressively gets worse.”

Detectives encourage parents to ask their children and teens specific questions.

“Who is this person, How do you know this person; just the general follow up questions as a parent,” Durham said. “Is this your friend? Have you ever met this person before? Do they go to your school? Have you seen them at school?”

Investigators asked parents to monitor the social media accounts and websites their children use while familiarizing themselves with new apps and technology available.

Reblogged from http://fox17.com/