Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-44645PUBLISHED: 2023-01-31
In Apache Linkis <=1.3.0 when used with the MySQL Connector/J, a deserialization vulnerability with possible remote code execution impact exists when an attacker has write access to a database and configures new datasource with a MySQL data source and malicious parameters. Therefore, the paramete...
CVE-2023-0591PUBLISHED: 2023-01-31
ubireader_extract_files is vulnerable to path traversal when run against specifically crafted UBIFS files, allowing the attacker to overwrite files outside of the extraction directory (provided the process has write access to that file or directory). This is due to the fact that a node name (dent_no...
CVE-2023-0592PUBLISHED: 2023-01-31A path traversal vulnerability affects jefferson's JFFS2 filesystem extractor. By crafting malicious JFFS2 files, attackers could force jefferson to write outside of the extraction directory.This issue affects jefferson: before 0.4.1.
CVE-2023-0593PUBLISHED: 2023-01-31A path traversal vulnerability affects yaffshiv YAFFS filesystem extractor. By crafting a malicious YAFFS file, an attacker could force yaffshiv to write outside of the extraction directory. This issue affects yaffshiv up to version 0.1 included, which is the most recent at time of publication.
CVE-2023-24829PUBLISHED: 2023-01-31
Incorrect Authorization vulnerability in Apache Software Foundation Apache IoTDB.This issue affects the iotdb-web-workbench component from 0.13.0 before 0.13.3. iotdb-web-workbench is an optional component of IoTDB, providing a web console of the database. This problem is fixed from version 0.13.3 o...
User Rank: Apprentice
9/18/2013 | 3:12:55 AM
Should we go back to doctors telling patients about getting a PHR too? Unless it is in a closed network not owned by an insurance company like Kaiser then they don't do it. Once upon a time and it was like pulling teeth I finally on Twitter got a couple of them to admit which PHR these use and so from there I just the rest don't use one and talk about it all the time as one thing I have found when folks don't want to reach out and help they usually themselves are "non participants" in the technology, hasn't failed me yet:)
I understand what the process here is for meaningful use and patients are losing their patience if you will. They know HIPAA is out there but then ask why does Walgreens or CVS share my prescription data, and then they get the answer and say why is it not covered by HIPAA so roll this in here too and sure it's hard. If they happen to roll over to my blog too then they know almost all the consumer devices are selling their data as well as the insurers so add this in on consent..it's a tough one but software won't solve it completely..human element called education on what they are signing needed...reading it is not enough in view of what else I outlined.
Back when I was developing stepping out in to the real world was something I learned as well as my perception and those of end users could be very different and after a couple knocks, with real life patients and not a survey, it kicked in so I realized too that I needed to be that role model as well and talk with people as they function and perceive in real life...took kit...well good luck:)