Bug 973479 - Prevent NUL characters from being accepted
Prevent NUL characters from being accepted
Status: CLOSED UPSTREAM
Product: Zanata
Classification: Community
Component: Component-Persistence (Show other bugs)
development
Unspecified Unspecified
medium Severity low
: ---
: ---
Assigned To: Sean Flanigan
Zanata-QA Mailling List
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-11 22:56 EDT by Sean Flanigan
Modified: 2015-07-28 23:35 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-28 23:35:42 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sean Flanigan 2013-06-11 22:56:39 EDT
Description of problem:

When exporting TMX, I found an instance of a NUL character (\0) in one of our HTextFlowTargets.  We need to fix our input validation in the client, in the server, and preferably in the database constraints to prevent this from happening again.

If we detect NUL in a user file, we should generate an error message which directs the user to the offending line.
Comment 2 Sean Flanigan 2014-03-20 20:45:52 EDT
Handy queries:

select * from HTextFlow where content0 LIKE CONCAT("%", CHAR(0x00 using utf8), "%");

select * from HTextFlowTarget where content0 LIKE CONCAT("%", CHAR(0x00 using utf8), "%");
Comment 3 Isaac Rooskov 2014-09-30 21:49:06 EDT
Set to low serverity as low occurance and easy user fix
Comment 4 Zanata Migrator 2015-07-28 23:35:42 EDT
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-337

Note You need to log in before you can comment on or make changes to this bug.